From: Richard Guenther <richard.guenther@gmail.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Binutils <binutils@sourceware.org>,
gdb-patches@sourceware.org, Nick Clifton <nickc@redhat.com>,
Jason Merrill <jason@redhat.com>
Subject: Re: [patch libiberty include gcc]: PR debug/28047 DWARF output_file_names should really understand DOS pathnames
Date: Sat, 26 Feb 2011 17:50:00 -0000 [thread overview]
Message-ID: <AANLkTik-AykoC1YU=YmEz6cG3XMJ-1a2FmMLwyTQSHTh@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiksVEpG9kF+rXGkxw06d4Y3aa+g7PFkddx-fTEG@mail.gmail.com>
On Sat, Feb 26, 2011 at 11:35 AM, Kai Tietz <ktietz70@googlemail.com> wrote:
> 2011/2/24 Jason Merrill <jason@redhat.com>:
>> OK (but you'll need to get a release manager to sign off if you want it in
>> 4.6, since it isn't a regression).
>>
>> Jason
>>
>
> Hi Richard,
>
> I would like to get this patch into 4.6. The outstanding issues about
> file/path-name comparsion in other places of gcc will be something for
> 4.7. But I would like to have the libiberty changes in as soon as
> possible, as those are of interest for some adjustments in binutils,
> too.
> So I want to ask if patch is ok for gcc, too?
I cannot comment about the libiberty pieces, those should get review
by a libiberty maintainer which should decide whether they are ok for 4.6.
If Jason is fine with the C++ changes I am, too.
Richard.
> Regards,
> Kai
>
next prev parent reply other threads:[~2011-02-26 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 9:50 Kai Tietz
2011-02-24 15:46 ` Jason Merrill
2011-02-26 10:35 ` Kai Tietz
2011-02-26 17:50 ` Richard Guenther [this message]
2011-02-27 10:58 ` Kai Tietz
2011-02-28 16:50 ` DJ Delorie
2011-02-28 18:37 ` Kai Tietz
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='AANLkTik-AykoC1YU=YmEz6cG3XMJ-1a2FmMLwyTQSHTh@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jason@redhat.com \
--cc=ktietz70@googlemail.com \
--cc=nickc@redhat.com \
/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).