From: Joseph Myers <joseph@codesourcery.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: <overseers@gcc.gnu.org>, <gcc@gcc.gnu.org>
Subject: Re: Separate commit mailing lists for trunk/branches possible?
Date: Fri, 17 Jul 2020 20:37:30 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2007172033530.16525@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.21.2007171838300.234068@eddie.linux-mips.org>
On Fri, 17 Jul 2020, Maciej W. Rozycki wrote:
> Would it be reasonable to have the mailing list split into more than one,
> that is at least the original covering the trunk, and then one or more for
> branches?
https://github.com/AdaCore/git-hooks/issues/10 is the issue for that
feature - implemented in the latest upstream version, but since merging
upstream with our local changes and testing a merge will be a large amount
of work, it seems sensible to wait for the other issues to be fixed first
(and probably for the copy of the hooks shared by binutils-gdb, glibc etc.
to be updated along with configuration for those repositories, first,
since that has many fewer local changes and eventually it would be good
for GCC to share that copy as well). In particular,
https://github.com/AdaCore/git-hooks/issues/9 is the issue regarding mails
for commits that are already in the repository.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-07-17 20:37 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
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 [this message]
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=alpine.DEB.2.21.2007172033530.16525@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=macro@linux-mips.org \
--cc=overseers@gcc.gnu.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).