From: Eli Zaretskii <eliz@gnu.org>
To: Aleksandar Ristovski <ARistovski@qnx.com>
Cc: drow@false.org, dje@google.com, gdb-patches@sources.redhat.com,
gcc-patches@gcc.gnu.org, RMansfield@qnx.com
Subject: Re: [patch] IS_ABSOLUTE_PATH to handle both DOS and POSIX path st yles
Date: Wed, 09 Jan 2008 19:10:00 -0000 [thread overview]
Message-ID: <usl16stnf.fsf@gnu.org> (raw)
In-Reply-To: <2F6320727174C448A52CEB63D85D11F40A76@nova.ott.qnx.com> (message from Aleksandar Ristovski on Wed, 9 Jan 2008 11:13:11 -0500)
> From: Aleksandar Ristovski <ARistovski@qnx.com>
> Cc: dje@google.com, gdb-patches@sources.redhat.com, gcc-patches@gcc.gnu.org, Ryan Mansfield <RMansfield@qnx.com>
> Date: Wed, 9 Jan 2008 11:13:11 -0500
>
> (This only works for drive letter in DOS paths, doesn't address the dir.
> Separator issue).
Right, and therefore why is it useful to consider partial solutions?
Can we at all use similar method to handle the slashes?
next prev parent reply other threads:[~2008-01-09 19:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 16:13 Aleksandar Ristovski
2008-01-09 19:10 ` Eli Zaretskii [this message]
2008-01-09 19:43 ` Daniel Jacobowitz
2008-01-10 4:13 ` Eli Zaretskii
2008-01-10 14:01 ` Daniel Jacobowitz
[not found] <2F6320727174C448A52CEB63D85D11F40A58@nova.ott.qnx.com>
[not found] ` <20080106054030.GA10410@caradoc.them.org>
2008-01-06 19:38 ` Eli Zaretskii
2008-01-06 20:03 ` Doug Evans
2008-01-06 20:18 ` Eli Zaretskii
2008-01-06 21:07 ` Doug Evans
2008-01-07 3:40 ` Daniel Jacobowitz
2008-01-07 4:21 ` Eli Zaretskii
2008-01-07 13:17 ` Daniel Jacobowitz
2008-01-07 21:28 ` Eli Zaretskii
2008-01-07 4:18 ` Eli Zaretskii
2008-01-07 17:36 ` Doug Evans
2008-01-07 21:32 ` Eli Zaretskii
2008-01-07 21:36 ` Daniel Jacobowitz
2008-01-08 4:25 ` Eli Zaretskii
2008-01-08 13:47 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2008-01-04 19:26 Aleksandar Ristovski
2008-01-04 19:33 ` Daniel Jacobowitz
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=usl16stnf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ARistovski@qnx.com \
--cc=RMansfield@qnx.com \
--cc=dje@google.com \
--cc=drow@false.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.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