From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Compilation warning in simple-object-xcoff.c
Date: Mon, 22 Jan 2018 04:27:00 -0000 [thread overview]
Message-ID: <20180122042744.c55gq3mh7hkp5msi@adacore.com> (raw)
In-Reply-To: <834lnfrzae.fsf@gnu.org>
> > I committed the patch.
>
> So now that this patch is committed to upstream libiberty, is it OK to
> push it to GDB's copy of the library?
Yes. For libiberty, incorporating patches from upstream is considered
an "obvious" change in the sense that it does not require prior
approval. We should actually always keep the two in sync, but as
we know, they easily forget, hence the occasion "resync" patches...
--
Joel
next prev parent reply other threads:[~2018-01-22 4:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 17:45 Eli Zaretskii
2018-01-16 18:01 ` DJ Delorie
2018-01-16 18:25 ` Eli Zaretskii
2018-01-16 18:38 ` DJ Delorie
2018-01-16 22:01 ` Andreas Schwab
2018-01-17 15:21 ` Eli Zaretskii
2018-01-17 20:48 ` DJ Delorie
2018-01-18 3:25 ` Eli Zaretskii
2018-01-20 12:48 ` Eli Zaretskii
2018-01-21 5:01 ` Ian Lance Taylor via gdb-patches
2018-01-21 15:45 ` Eli Zaretskii
2018-01-21 15:45 ` Eli Zaretskii
2018-01-22 4:27 ` Joel Brobecker [this message]
2018-01-27 16:43 ` Eli Zaretskii
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=20180122042744.c55gq3mh7hkp5msi@adacore.com \
--to=brobecker@adacore.com \
--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