From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: remove unused includes from dwarf2read.c
Date: Mon, 14 Oct 2019 14:39:00 -0000 [thread overview]
Message-ID: <83r23fie80.fsf@gnu.org> (raw)
In-Reply-To: <1c1f820fa507243fd7a2096ec3eb2454@polymtl.ca> (message from Simon Marchi on Mon, 14 Oct 2019 10:21:50 -0400)
> 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?
next prev parent reply other threads:[~2019-10-14 14:39 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 [this message]
2019-10-14 15:18 ` Simon Marchi
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=83r23fie80.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.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