From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: 3 weeks to GDB 7.9.1 release?
Date: Wed, 22 Apr 2015 14:31:00 -0000 [thread overview]
Message-ID: <20150422143120.GJ4764@adacore.com> (raw)
In-Reply-To: <83y4lk2ria.fsf@gnu.org>
> Not really blocking, but would someone please help me get these
> annoyances fixed upstream, so that I don't need to continue fixing
> them in every GDB release?
>
> http://lists.gnu.org/archive/html/bug-binutils/2015-03/msg00115.html
IIUC (quick read only), you need libiberty patches to be pushed?
libiberty is owned by GCC, and so such pushes should just be pushed
to GCC's SVN first, and then can be backported to binutils-gdb...
Do you have SVN write access to GCC?
--
Joel
next prev parent reply other threads:[~2015-04-22 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 13:32 Joel Brobecker
2015-04-22 13:59 ` Eli Zaretskii
2015-04-22 14:31 ` Joel Brobecker [this message]
2015-04-22 14:38 ` Eli Zaretskii
2015-04-22 15:22 ` Pierre Muller
2015-04-22 17:14 ` Joel Brobecker
2015-05-02 15:33 ` Doug Evans
2015-05-02 22:46 ` Pierre Muller
2015-05-04 12:12 ` Joel Brobecker
2015-05-01 22:23 ` Sergio Durigan Junior
2015-05-02 15:29 ` Doug Evans
2015-05-06 13:42 ` 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=20150422143120.GJ4764@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