Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Cc: dje@google.com
Subject: Re: [rfc] Use substitute-path for filename portion too
Date: Fri, 08 Feb 2008 22:21:00 -0000	[thread overview]
Message-ID: <20080208222124.GB10092@caradoc.them.org> (raw)
In-Reply-To: <20080207174645.GA19452@caradoc.them.org>

On Thu, Feb 07, 2008 at 12:46:45PM -0500, Daniel Jacobowitz wrote:
> I borrowed this bit from Doug's work on canonicalizing filenames last
> month.  We ended up without that patch, but does anyone see a problem
> with just this part?

As no one did, and most of the participants of the recent discussion
agreed, I've checked this in.

-- 
Daniel Jacobowitz
CodeSourcery


      parent reply	other threads:[~2008-02-08 22:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 17:47 Daniel Jacobowitz
2008-02-07 17:57 ` Joel Brobecker
2008-02-07 18:14   ` Daniel Jacobowitz
2008-02-07 18:28     ` Joel Brobecker
2008-02-07 18:51       ` Aleksandar Ristovski
2008-02-08 15:02       ` Eli Zaretskii
2008-02-08  0:31     ` Doug Evans
2008-02-08 22:20       ` Daniel Jacobowitz
2008-02-08 22:21 ` Daniel Jacobowitz [this message]

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=20080208222124.GB10092@caradoc.them.org \
    --to=drow@false.org \
    --cc=dje@google.com \
    --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