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: joseph@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: Multiple identical mails from Gerrit
Date: Sat, 23 Nov 2019 07:17:00 -0000	[thread overview]
Message-ID: <83imnbuknp.fsf@gnu.org> (raw)
In-Reply-To: <545dd677-52a2-5e04-536d-5af4d6850b83@simark.ca> (message from	Simon Marchi on Fri, 22 Nov 2019 17:03:54 -0500)

> Cc: gdb-patches@sourceware.org
> From: Simon Marchi <simark@simark.ca>
> Date: Fri, 22 Nov 2019 17:03:54 -0500
> 
> >> 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.

My problem with these messages is that I have to look at the fine
details of the Subject line, and perhaps also at the beginning of the
body, to understand whether I need to review the patch.  Since I only
review the documentation parts, and rarely look at other parts of the
changeset, it is important for me to be able to quickly understand
whether a posted patch needs my attention.  And these messages, which
look almost exactly like an RFA but for minor details, make this
harder.

But maybe I'm the only one who is in this situation, in which case
I'll have to live with this.

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

Thanks you.

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

Yep.  So maybe this issue is of academic importance ;-)


      reply	other threads:[~2019-11-23  7:17 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
2019-11-23  7:17         ` Eli Zaretskii [this message]

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=83imnbuknp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.com \
    --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