From: Joseph Myers <joseph@codesourcery.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
Carlos O'Donell <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Setup non-pushing gerrit instance for glibc.
Date: Mon, 28 Oct 2019 22:59:56 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1910282245340.6534@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20191028191749.GA12487@google.com>
On Mon, 28 Oct 2019, Jonathan Nieder wrote:
> > (b) not losing the quoted text
> > being replied to which is important to understanding the replies.
>
> Can you say more about this (e.g. do you have an example)?
My example is from GDB.
https://sourceware.org/ml/gdb-patches/2019-10/msg00942.html was a message
sent to gerrit, in reply to a comments message.
Now look at that one in gerrit -
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/126 - or as it came
back to the list from gerrit -
https://sourceware.org/ml/gdb-patches/2019-10/msg00943.html - and note
that in gerrit's version, the first paragraph "On 2019-10-26 7:10 p.m.,
Tom Tromey (Code Review) wrote:" is followed by the next paragraph *after*
the quoted text - the quoted text in between has been lost (Simon's
comment in gerrit two comments later clarifies for gerrit readers, "I
replied by email, so that's the header my email client added when replying
to Tom's comment, and Gerrit interpreted it as part of my comment.").
The problem of course isn't that gerrit kept that heading text, it's that
it lost the quoted text after it. Removing quoted text at the end of the
message makes sense, but removing quoted text that's followed by comments
doesn't.
(The examples in the gerrit documentation of email handling suggest it's
already *supposed* to handle inline replies interspersed with quoted text,
not just pure top-posting, but it evidently mishandled this particular
email.)
> > * Handle email replies to notifications of new patches, not just to
> > comments on them.
>
> I would expect this to already work as well.
So would I; only handling replies to comments seems an odd limitation. I
haven't verified if it does or not; I'm just going on what
https://sourceware.org/ml/libc-alpha/2019-10/msg00812.html says about "We
will also have to warn the user that replying directly to a new change
message will not work; gerrit can only understand email replies to
comments.".
> > * Include diff hunks in emails with comments on changed code (we now have
> > more context in the code quoted, which is an improvement, but seeing the
> > actual *changes* being commented on, rather than just one version of the
> > code, is important to provide sufficient information in many cases).
>
> This is related to https://crbug.com/gerrit/11804, but it's not quite
> the same. It sounds like you'd like the snippets to be in unified
> diff format (which makes sense to me).
Yes. Giving snippets in diff format (assuming there actually are changes
around the code in question rather than someone commenting on unmodified
code) is a reasonable heuristic to give the relevant information in 90% of
cases. (The remaining 10% includes cases that already exist where e.g.
reordering code in the file means the diff output isn't very helpful
anyway, and whatever gerrit does then would be no worse than quoting an
unhelpful diff in a manually sent email.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-10-28 23:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 19:39 Setup non-pushing gerrit instance for glibc Carlos O'Donell
2019-10-24 21:41 ` Joseph Myers
2019-10-25 0:43 ` Ian Kent
2019-10-25 1:16 ` Jonathan Nieder
2019-10-25 10:21 ` Ian Kent
2019-10-25 1:02 ` Carlos O'Donell
2019-10-25 2:04 ` Sergio Durigan Junior
2019-10-25 3:14 ` Simon Marchi
2019-10-25 4:10 ` Simon Marchi
2019-10-25 14:48 ` Joseph Myers
2019-10-25 15:48 ` Simon Marchi
2019-10-25 16:10 ` Joseph Myers
2019-10-25 16:28 ` Simon Marchi
2019-10-25 1:25 ` Jonathan Nieder
2019-10-25 14:09 ` Florian Weimer
2019-10-25 15:18 ` Joseph Myers
2019-10-25 17:00 ` Sergio Durigan Junior
2019-10-25 20:33 ` Joseph Myers
2019-10-25 21:06 ` Sergio Durigan Junior
2019-10-25 21:13 ` Joseph Myers
2019-10-27 22:12 ` Sergio Durigan Junior
2019-10-28 17:58 ` Joseph Myers
2019-10-28 19:17 ` Jonathan Nieder
2019-10-28 22:59 ` Joseph Myers [this message]
2019-10-29 1:21 ` Sergio Durigan Junior
2019-10-25 22:03 ` Jonathan Nieder
2019-10-26 13:53 ` Carlos O'Donell
2019-10-30 18:25 ` Szabolcs Nagy
2019-11-12 18:53 ` Gabriel F. T. Gomes
2019-11-12 19:21 ` Carlos O'Donell
2019-11-12 19:59 ` Florian Weimer
2019-11-12 20:02 ` Jonathan Nieder
2019-11-12 21:10 ` Gabriel F. T. Gomes
2019-11-12 21:13 ` Carlos O'Donell
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1910282245340.6534@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=jrnieder@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=sergiodj@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).