From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>, DJ Delorie <dj@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: MinGW compilation warnings in libiberty's waitpid.c
Date: Sat, 27 May 2017 15:58:00 -0000 [thread overview]
Message-ID: <CABOHX+fMeV9K1ZiO510QfczdFPK6+MpgkopCAjiyg7c8PqkAtg@mail.gmail.com> (raw)
In-Reply-To: <20170526163053.aj22jelqmoeo7wvd@adacore.com>
On 26 May 2017 at 18:30, Joel Brobecker <brobecker@adacore.com> wrote:
>> Thanks. Is the environ thing also fixed?
>>
>> Joel/Pedro, how should I go about making sure these changes are in the
>> GDB copy of libiberty?
>
> Normally, I'd expect someone pushing to GCC's libibert to also
> update our repo accordingly. However, it's easy to forget so,
> if you notice a change that was not propagated to us, we just
> cherry-pick those changes so as to make sure our copy is up
> to date with GCC's. We also see the occasional "resync libiberty"
> commits which act as a failsafe, but I don't think we should wait
> for one of those.
>
This has been on my todo-list for a little while, as re-syncing is
something I normally do after pushing D language support updates into
libiberty. However I decided to give it a wait until I got all
pending patches in, the last of which I'm just pushing in now.
Regards,
Iain.
next prev parent reply other threads:[~2017-05-27 11:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 15:30 Eli Zaretskii
2017-05-19 15:40 ` Pedro Alves
2017-05-19 17:26 ` Eli Zaretskii
2017-05-20 5:02 ` DJ Delorie
2017-05-21 16:12 ` Eli Zaretskii
2017-05-22 19:55 ` DJ Delorie
2017-05-23 19:26 ` Eli Zaretskii
2017-05-23 19:38 ` DJ Delorie
2017-05-24 2:26 ` Eli Zaretskii
2017-05-24 3:31 ` DJ Delorie
2017-05-24 18:47 ` Eli Zaretskii
2017-05-24 22:16 ` DJ Delorie
2017-05-26 8:54 ` Eli Zaretskii
2017-05-26 16:38 ` Joel Brobecker
2017-05-26 18:04 ` Eli Zaretskii
2017-05-27 0:28 ` Joel Brobecker
2017-05-26 18:14 ` DJ Delorie
2017-05-27 15:58 ` Iain Buclaw [this message]
2017-05-30 17:23 ` Joel Brobecker
2017-06-06 17:54 ` Iain Buclaw
2017-06-07 12:38 ` Joel Brobecker
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=CABOHX+fMeV9K1ZiO510QfczdFPK6+MpgkopCAjiyg7c8PqkAtg@mail.gmail.com \
--to=ibuclaw@gdcproject.org \
--cc=brobecker@adacore.com \
--cc=dj@redhat.com \
--cc=eliz@gnu.org \
--cc=gcc-patches@gcc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).