From: Simon Marchi <simon.marchi@polymtl.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: remove unused includes from dwarf2read.c
Date: Mon, 14 Oct 2019 15:18:00 -0000 [thread overview]
Message-ID: <ee153091c2ba2528e9e8fd3d33f55d36@polymtl.ca> (raw)
In-Reply-To: <83r23fie80.fsf@gnu.org>
On 2019-10-14 10:38, Eli Zaretskii wrote:
>> Date: Mon, 14 Oct 2019 10:21:50 -0400
>> From: Simon Marchi <simon.marchi@polymtl.ca>
>>
>> I pushed it after Tom de Vries reviewed it on Gerrit:
>>
>> https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/24
>
> Does this mean that now we need to look for patches in two places?
> Can Gerrit be set up to forward the review comments to the list?
>
> Also, if some of us decides to do the review on Gerrit, does it mean
> all the others need to do that as well?
Hi Eli,
Yes, Gerrit can be set to send notifications to an arbitrary email, so
we can set it to send them to gdb-patches. We have talked about that
earlier, it's just not done yet. I'll look into it right now.
As long as we use Gerrit and mail patches in parallel, people are free
to send patches using the system they prefer. I think it's simpler if
reviewers use the system that was chosen by the patch author (reply on
Gerrit if the patch is on Gerrit, reply by email if the patch is by
email).
In theory, it is possible to reply to some of Gerrit's email
notifications:
https://gerrit-review.googlesource.com/Documentation/intro-user.html#reply-by-email
But our server isn't configured to receive emails for the moment, so
that won't work. Reading this page, I'm not sure if responding to a
"New change" notification would work, we'd have to try it.
Simon
next prev parent reply other threads:[~2019-10-14 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 4:54 Simon Marchi
2019-10-14 14:22 ` Simon Marchi
2019-10-14 14:39 ` Eli Zaretskii
2019-10-14 15:18 ` Simon Marchi [this message]
2019-10-14 17:12 ` Gerrit (was: [PATCH] gdb: remove unused includes from dwarf2read.c) Eli Zaretskii
2019-10-14 17:31 ` Gerrit Simon Marchi
2019-10-14 17:56 ` Gerrit Eli Zaretskii
2019-10-14 18:03 ` Gerrit Tom Tromey
2019-10-14 18:32 ` Gerrit Eli Zaretskii
2019-10-15 1:33 ` Gerrit Simon Marchi
2019-10-15 8:51 ` Gerrit Eli Zaretskii
2019-10-15 15:57 ` Gerrit Sergio Durigan Junior
2019-10-15 16:33 ` Gerrit Eli Zaretskii
2019-10-15 17:09 ` Gerrit Sergio Durigan Junior
2019-10-15 17:31 ` Gerrit Eli Zaretskii
2019-10-15 17:49 ` Gerrit Sergio Durigan Junior
2019-10-14 23:51 ` Gerrit Simon Marchi
2019-10-14 18:02 ` [PATCH] gdb: remove unused includes from dwarf2read.c Luis Machado
2019-10-14 20:58 ` 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=ee153091c2ba2528e9e8fd3d33f55d36@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@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