Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Christian Biesinger <cbiesinger@google.com>
Cc: Andreas Schwab <schwab@suse.de>,  Tom Tromey <tom@tromey.com>,
	 gdb-patches <gdb-patches@sourceware.org>
Subject: Re: some thoughts on gerrit
Date: Mon, 21 Oct 2019 21:24:00 -0000	[thread overview]
Message-ID: <8736fl7px1.fsf@redhat.com> (raw)
In-Reply-To: <CAPTJ0XHa97vx+pBPnkn7jJPqQ0eC4mP+2HOhuQbNN43QzwN9jQ@mail.gmail.com>	(Christian Biesinger's message of "Mon, 21 Oct 2019 15:59:04 -0500")

On Monday, October 21 2019, Christian Biesinger wrote:

> FWIW, I filed https://bugs.chromium.org/p/gerrit/issues/detail?id=11791
> and reopened https://bugs.chromium.org/p/gerrit/issues/detail?id=924

Thanks, Christian.

I think the two bugs are closely related.  If gerrit doesn't send a
cover letter, then it's hard to thread the emails.  One can argue that
the first patch should become the root message, but it's not so
organized.  A cover letter really simplifies things in this case.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2019-10-21 21:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-20 14:37 Tom Tromey
2019-10-20 22:25 ` Sergio Durigan Junior
2019-10-20 22:30   ` Sergio Durigan Junior
2019-10-21  9:02   ` Andreas Schwab
2019-10-21 20:59     ` Christian Biesinger via gdb-patches
2019-10-21 21:24       ` Sergio Durigan Junior [this message]
2019-10-21 21:25     ` Sergio Durigan Junior
2019-10-20 23:17 ` Andrew Pinski
2019-10-21  1:49   ` Simon Marchi
2019-10-21  3:26 ` Simon Marchi

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=8736fl7px1.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@suse.de \
    --cc=tom@tromey.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