Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: Multiple identical mails from Gerrit
Date: Fri, 22 Nov 2019 21:07:00 -0000	[thread overview]
Message-ID: <83lfs7vcvu.fsf@gnu.org> (raw)
In-Reply-To: <1db7ebdb-e98b-ba9b-2ac5-e454a1832578@simark.ca> (message from	Simon Marchi on Fri, 22 Nov 2019 15:53:42 -0500)

> 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?

> 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...

Maybe I made a mistake counting emails, there were several similar
ones.


  reply	other threads:[~2019-11-22 21:07 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 [this message]
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=83lfs7vcvu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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