From: Florian Weimer <fw@deneb.enyo.de>
To: Carlos O'Donell via Gcc <gcc@gcc.gnu.org>
Cc: Overseers mailing list <overseers@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>,
overseers@gcc.gnu.org, "Frank Ch. Eigler" <fche@elastic.org>
Subject: Re: Separate commit mailing lists for trunk/branches possible?
Date: Fri, 17 Jul 2020 21:41:12 +0200 [thread overview]
Message-ID: <87r1ta0w13.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <c987d864-79a0-4f92-872d-40a670150adb@redhat.com> (Carlos O'Donell via Gcc's message of "Fri, 17 Jul 2020 14:46:38 -0400")
* Carlos O'Donell via Gcc:
> FYI, for glibc we use the AdaCore git commit hooks (like gdb).
>
> There we use this configuration:
>
> # Only send emails for master and release branches.
> no-emails = refs/heads/(?!master|release.*)
>
> This way you don't get vendor branch commit emails.
I think this only affects the Bugzilla gateway (which is broken anyway
because it doesn't extract bug numbers from the commit subject).
Anyway, there are a ton of commit notifications for personal branches:
<https://sourceware.org/pipermail/glibc-cvs/2020q3/thread.html>
next prev parent reply other threads:[~2020-07-17 19:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 18:05 Maciej W. Rozycki
2020-07-17 18:11 ` Frank Ch. Eigler
2020-07-17 18:46 ` Carlos O'Donell
2020-07-17 19:41 ` Florian Weimer [this message]
2020-07-17 20:47 ` Carlos O'Donell
2020-07-17 20:50 ` Joseph Myers
2020-07-17 20:55 ` Frank Ch. Eigler
2020-07-17 19:48 ` Christopher Faylor
2020-07-19 20:57 ` Maciej W. Rozycki
2020-07-19 21:15 ` Frank Ch. Eigler
2020-07-19 21:56 ` Maciej W. Rozycki
2020-07-17 20:37 ` Joseph Myers
2021-09-27 14:48 overseers&gcc gnu org
2021-10-08 10:49 Maciej W. Rozycki
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=87r1ta0w13.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=carlos@redhat.com \
--cc=fche@elastic.org \
--cc=gcc@gcc.gnu.org \
--cc=overseers@gcc.gnu.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).