Re: Question about git: merging to gccgo branch

2020-03-31 Thread Martin Liška
On 3/30/20 7:54 PM, Joseph Myers wrote: Email sending for user branches makes perfect sense, to make visible the development going on. If so, can we then come up with a naming convention that will block the email sending. I mean something like me/PR123456-fix-that-private? I see the limitation

Re: Question about git: merging to gccgo branch

2020-03-30 Thread Joseph Myers
On Mon, 30 Mar 2020, Ian Lance Taylor via Gcc wrote: > On Mon, Mar 30, 2020 at 10:54 AM Joseph Myers wrote: > > > > On Mon, 30 Mar 2020, Martin Liška wrote: > > > > > Can you please disable email sending for user branch? Or does it make any > > > sense? > > > > Email sending for user branches mak

Re: Question about git: merging to gccgo branch

2020-03-30 Thread Ian Lance Taylor via Gcc
On Mon, Mar 30, 2020 at 10:54 AM Joseph Myers wrote: > > On Mon, 30 Mar 2020, Martin Liška wrote: > > > Can you please disable email sending for user branch? Or does it make any > > sense? > > Email sending for user branches makes perfect sense, to make visible the > development going on. It's sp

Re: Question about git: merging to gccgo branch

2020-03-30 Thread Joseph Myers
On Mon, 30 Mar 2020, Martin Liška wrote: > Can you please disable email sending for user branch? Or does it make any > sense? Email sending for user branches makes perfect sense, to make visible the development going on. It's specifically email sending for merges of commits already present in

Re: Question about git: merging to gccgo branch

2020-03-30 Thread Martin Liška
On 1/22/20 7:38 PM, Joseph Myers wrote: On Wed, 22 Jan 2020, Ian Lance Taylor wrote: I don't want to send 581 e-mails. I would be happy not sending any e-mails at all. I would also be happy sending 1 e-mail. This is the issue we've discussed in

Re: Question about git: merging to gccgo branch

2020-01-22 Thread Joseph Myers
On Wed, 22 Jan 2020, Ian Lance Taylor wrote: > Thanks. Should I go ahead and commit and generate 581 e-mail > messages, or should I wait? In order to keep up with the Go release > cycle I'd like to commit this merge soon if possible. I suggest going ahead and committing. -- Joseph S. Myers jo

Re: Question about git: merging to gccgo branch

2020-01-22 Thread Ian Lance Taylor
On Wed, Jan 22, 2020 at 10:39 AM Joseph Myers wrote: > > On Wed, 22 Jan 2020, Ian Lance Taylor wrote: > > > I don't want to send 581 e-mails. I would be happy not sending any > > e-mails at all. I would also be happy sending 1 e-mail. > > This is the issue we've discussed in >

Re: Question about git: merging to gccgo branch

2020-01-22 Thread Joseph Myers
On Wed, 22 Jan 2020, Ian Lance Taylor wrote: > I don't want to send 581 e-mails. I would be happy not sending any > e-mails at all. I would also be happy sending 1 e-mail. This is the issue we've discussed in and the messages linked from there.

Question about git: merging to gccgo branch

2020-01-22 Thread Ian Lance Taylor
I'm trying to merge trunk revision 7c46e71d016c86971ac26c6fa38d76482859f296 to the gccgo branch. I did this by checking out the branch ("git checkout origin/devel/gccgo") and running "git merge master". I'm not sure whether I should keep reporting this kind of operation to gcc-patches now that we