From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Jonathan Nieder <jrnieder@gmail.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 21:21:26 -0400 [thread overview]
Message-ID: <87sgncfisp.fsf@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1910282245340.6534@digraph.polyomino.org.uk> (Joseph Myers's message of "Mon, 28 Oct 2019 22:59:56 +0000")
On Monday, October 28 2019, Joseph Myers wrote:
> On Mon, 28 Oct 2019, Jonathan Nieder wrote:
>> > * 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.".
That's correct: replying directly to a new change notification does not
work. Gerrit cannot parse the email due. The only thing that works is
replying to a comment.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2019-10-29 1:21 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
2019-10-29 1:21 ` Sergio Durigan Junior [this message]
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=87sgncfisp.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=jrnieder@gmail.com \
--cc=libc-alpha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).