From: Simon Marchi <simark@simark.ca>
To: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: Multiple identical mails from Gerrit
Date: Fri, 22 Nov 2019 20:53:00 -0000 [thread overview]
Message-ID: <1db7ebdb-e98b-ba9b-2ac5-e454a1832578@simark.ca> (raw)
In-Reply-To: <83wobrvhv2.fsf@gnu.org>
On 2019-11-22 2:19 p.m., Eli Zaretskii wrote:
> Is there any reason why some (or all?) email messages from Gerrit
> arrive at my inbox several times? For example, this message:
>
> From: "Sourceware to Gerrit sync (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
> To: Christian Biesinger <cbiesinger@google.com>, Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
> Auto-Submitted: auto-generated
> Subject: [pushed] Replace SYMBOL_*_NAME accessors with member functions
>
> arrived as 3 identical messages.
>
> Why does this happen?
>
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.
When I'm not subscribed to a particular change (because I'm not a reviewer or in
the CC list), I receive these two emails from the list. When I am subscribed to
a change, I receive these two emails twice (once through the list and once
directly to my email), for a total of 4.
I don't know why you have 3 messages for this change, this is an odd number, and
you are not subscribed to it either...
Simon
next prev parent reply other threads:[~2019-11-22 20:53 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 [this message]
2019-11-22 21:07 ` Eli Zaretskii
2019-11-22 21:11 ` Joseph Myers
2019-11-22 22:03 ` Simon Marchi
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=1db7ebdb-e98b-ba9b-2ac5-e454a1832578@simark.ca \
--to=simark@simark.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@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