Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Joseph Myers <joseph@codesourcery.com>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Multiple identical mails from Gerrit
Date: Fri, 22 Nov 2019 22:03:00 -0000	[thread overview]
Message-ID: <545dd677-52a2-5e04-536d-5af4d6850b83@simark.ca> (raw)
In-Reply-To: <alpine.DEB.2.21.1911222110240.28545@digraph.polyomino.org.uk>

On 2019-11-22 4:11 p.m., Joseph Myers wrote:
> On Fri, 22 Nov 2019, Eli Zaretskii wrote:
> 
>>> From: Simon Marchi <simark@simark.ca>
>>> Date: Fri, 22 Nov 2019 15:53:42 -0500
>>>
>>> When a patch with a Change-Id corresponding to an open Gerrit change is manually
>>> pushed to the binutils-gdb git repo, Gerrit notices it and that automatically
>>> creates a new version of the change, reflecting what was actually pushed.  That
>>> sends a mail of type "new patchset version".  It then changes the state to
>>> "Closed", which sends another email.
>>
>> Why do these trigger sending email at all?  We didn't get email about
>> pushing changesets before Gerrit, so why do we need them now?
>
> On the glibc side, I tend to agree with that - people wanting to see what 
> was pushed to master can follow glibc-cvs.

I think that having a notification saying that the patch was pushed is nice.  People
reply "I pushed the patch",  so we might as well let the system do it automatically
anyway.

I could maybe get rid of the second one (state change), I'll have to look in the configuration.

Anyway: https://sourceware.org/ml/gdb-patches/2019-11/msg00749.html

Simon


  reply	other threads:[~2019-11-22 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22 19:19 Eli Zaretskii
2019-11-22 20:53 ` Simon Marchi
2019-11-22 21:07   ` Eli Zaretskii
2019-11-22 21:11     ` Joseph Myers
2019-11-22 22:03       ` Simon Marchi [this message]
2019-11-23  7:17         ` Eli Zaretskii

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=545dd677-52a2-5e04-536d-5af4d6850b83@simark.ca \
    --to=simark@simark.ca \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.com \
    /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