From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA] Add -s option to source command.
Date: Mon, 12 Apr 2010 17:33:00 -0000 [thread overview]
Message-ID: <v2oe394668d1004121033u451fa3a9qff8e58dc0fb5457a@mail.gmail.com> (raw)
In-Reply-To: <o2he394668d1004121031gee9183c8g3aa53b249827c121@mail.gmail.com>
On Mon, Apr 12, 2010 at 10:31 AM, Doug Evans <dje@google.com> wrote:
> I'm all for stripping the drive letter if it's agreeable to everyone else.
> I will send this to the binutils list for approval tomorrow, unless
> someone has a better suggestion.
>
> openp would then check HAVE_DRIVE_SPEC (path) and if true call
> STRIP_DRIVE_SPEC (path)
> before concatenating the search path with the user-provided path.
>
> I put these macros in filenames.h because that's where
> IS_ABSOLUTE_PATH and IS_DIR_SEPARATOR live.
>
> 2010-04-12 Doug Evans <dje@google.com>
>
> * filenames.h (HAVE_DRIVE_SPEC, STRIP_DRIVE_SPEC): New macros.
... or is this another file that gets migrated over from the gcc tree,
and thus needs approval from the gcc list ...
next prev parent reply other threads:[~2010-04-12 17:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 21:58 Doug Evans
2010-04-06 23:17 ` Doug Evans
2010-04-07 20:14 ` Tom Tromey
2010-04-08 22:49 ` Doug Evans
2010-04-08 23:09 ` Sergio Durigan Junior
2010-04-09 0:13 ` Doug Evans
2010-04-09 17:15 ` Tom Tromey
2010-04-09 17:48 ` Eli Zaretskii
2010-04-10 1:29 ` Joel Brobecker
2010-04-09 7:49 ` Eli Zaretskii
2010-04-09 17:23 ` Doug Evans
2010-04-09 17:46 ` Eli Zaretskii
2010-04-09 18:12 ` Doug Evans
2010-04-09 19:31 ` Eli Zaretskii
2010-04-09 19:49 ` Doug Evans
2010-04-12 17:31 ` Doug Evans
2010-04-12 17:33 ` Doug Evans [this message]
2010-04-12 17:47 ` Tom Tromey
2010-04-12 17:54 ` Eli Zaretskii
2010-04-14 22:01 ` Doug Evans
2010-04-15 3:10 ` Eli Zaretskii
2010-04-09 17:13 ` Tom Tromey
2010-04-09 17:15 ` Doug Evans
2010-04-09 17:19 ` Tom Tromey
2010-04-17 15:20 ` H.J. Lu
2010-04-20 5:38 ` Doug Evans
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=v2oe394668d1004121033u451fa3a9qff8e58dc0fb5457a@mail.gmail.com \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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