public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ivo Raisr <ivosh@ivosh.net>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org
Subject: Re: Fwd: hosting Valgrind repository on sourceware.org
Date: Thu, 16 Feb 2017 08:38:00 -0000	[thread overview]
Message-ID: <CANXv6=uvmZQr+ie5ke6RCkgmzh-p32QiWBgCZ+qJQFdjSY=gdg@mail.gmail.com> (raw)
In-Reply-To: <20170209224434.GM41423@elastic.org>

Hi Frank,
I would like confirm with you about possibility of sending
notifications about pushed commits
to Valgrind repo. I think for example both glibc and gdb have setup
post-receive hook so their alias gets an email when a push happens.
Is that something we can (re)use for Valgrind as well? However we would like
to get notification only when a push was done for master branch; for example
as discussed here:
http://stackoverflow.com/questions/7351551/writing-a-git-post-receive-hook-to-deal-with-a-specific-branch

Thank you,
I.

  reply	other threads:[~2017-02-16  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANXv6=u0Sp=Q=9=DPBEbniSKsmdNwZNLLvydnB7+7Y9321PZhw@mail.gmail.com>
     [not found] ` <CANXv6=v5AkH=fvPQf1YDKyeqeCgzyDeVRmzuQDRb=XeFcnh-PA@mail.gmail.com>
     [not found]   ` <CANXv6=s75bVxUNSoP=Vqk7EXETArDDC5w3vtR+ZZBa2sWrAqig@mail.gmail.com>
     [not found]     ` <20170204225408.GF41423@elastic.org>
     [not found]       ` <CANXv6=vDYO7fbgygr9uHphMqQQFeCA3eNuaNdcg5GPZWyFPRTA@mail.gmail.com>
     [not found]         ` <20170206160126.GH41423@elastic.org>
     [not found]           ` <CANXv6=vx+2hZZzXq+BOHD6h0aq011isAjq0n7-yUZrxi4yDbfQ@mail.gmail.com>
2017-02-06 21:05             ` Frank Ch. Eigler
2017-02-09 22:37               ` Ivo Raisr
2017-02-09 22:44                 ` Frank Ch. Eigler
2017-02-16  8:38                   ` Ivo Raisr [this message]
2017-02-16 18:48                     ` Frank Ch. Eigler
2017-02-16 19:30                       ` Andrew Pinski
2017-02-24 16:08               ` Ivo Raisr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANXv6=uvmZQr+ie5ke6RCkgmzh-p32QiWBgCZ+qJQFdjSY=gdg@mail.gmail.com' \
    --to=ivosh@ivosh.net \
    --cc=fche@elastic.org \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).