This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc-cvs mails for personal/vendor branches for merge commits
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, "Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>, <gcc at gcc dot gnu dot org>
- Date: Fri, 17 Jan 2020 16:47:29 +0000
- Subject: Re: gcc-cvs mails for personal/vendor branches for merge commits
- Ironport-sdr: 7xQsUcLS3ymrxPCs3lhCIILr/mDKpey83TwQ4tSfVyllKAjXHHxgTOqKEpMTrvMPX+LSOAZJ02 OjQ4FpQtKzLolNyWhAri+oAAxh++GWLq6z6tbVss+ylyvU/0VZgpg7/sPUEV+tmT1k8pnwSvVY bMpgMuPCdK8KNuxYpwBRo3vu4WhT37seDnJfTY1HBCDzYUQyvAyhFdTE7XzBrGyr5T4I8y/2xQ dqzNYNLHjltWMK776p6RiC5xR3kOwqUr8DriZnzXQyxlq2BuA5D9heBsRPEv+Gv8UcjqscYwP9 SFM=
- Ironport-sdr: TERsGHuwaJgYTyuVmsYzvJqb8XueLUSoZ+Ph68vbT2z2vdPCvgh1JzSgEA0U/bvQJSzw24TM5X unNywPelAabI39jKjAGrT46dLhsWGn7047f1bAEEO/iN5A90ylFbJOafIjGW5TX5ozlLu47rRn 8thhFuKhhWrpz8ANScFBrsKv66Nh4zb+aiRamOeQr3mplKi1XBdneWSxFOi4z6ooKorC3Cy/hk Z1Ha468BJGCOnp0geL871l7x3gtpbrXGCNWAPggMCl6ZxbW1Wq+PiNoxwVhlqPEfE4jNgaDhm2 +nE=
- References: <20200115141617.GS10088@tucnak> <alpine.DEB.2.21.2001151448060.11538@digraph.polyomino.org.uk> <20200116114002.GB13162@adacore.com> <alpine.DEB.2.21.2001161431290.18540@digraph.polyomino.org.uk> <20200117154928.GB4164@adacore.com>
On Fri, 17 Jan 2020, Joel Brobecker wrote:
> Would it be sufficient to say that some branches would only
> trigger a summary email, but not individual commit emails?
Maybe that will end up being appropriate for users / vendors branches, if
we can't effectively distinguish rebased commits from new ones. But for
shared fast-forward-only development branches, I think the individual
commit emails are appropriate for commits new to the branch, while a
summary email is appropriate for merges to the branch.
--
Joseph S. Myers
joseph@codesourcery.com