From: DJ Delorie <dj@redhat.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: ktietz70@googlemail.com, gcc-patches@gcc.gnu.org,
binutils@sourceware.org, gdb-patches@sourceware.org,
nickc@redhat.com, jason@redhat.com
Subject: Re: [patch libiberty include gcc]: PR debug/28047 DWARF output_file_names should really understand DOS pathnames
Date: Mon, 28 Feb 2011 16:50:00 -0000 [thread overview]
Message-ID: <201102281650.p1SGoFQv018877@greed.delorie.com> (raw)
In-Reply-To: <AANLkTik-AykoC1YU=YmEz6cG3XMJ-1a2FmMLwyTQSHTh@mail.gmail.com> (message from Richard Guenther on Sat, 26 Feb 2011 18:50:40 +0100)
The libiberty parts are OK
next prev parent reply other threads:[~2011-02-28 16: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
2011-02-27 10:58 ` Kai Tietz
2011-02-28 16:50 ` DJ Delorie [this message]
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=201102281650.p1SGoFQv018877@greed.delorie.com \
--to=dj@redhat.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 \
--cc=richard.guenther@gmail.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).