From: Eli Zaretskii <eliz@gnu.org>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: mark.kettenis@xs4all.nl, gdb@sourceware.org
Subject: Re: [patch gdb]: Fix some DOS-path related issues in gdb
Date: Thu, 03 Mar 2011 13:13:00 -0000 [thread overview]
Message-ID: <E1Pv8LY-0005tI-7d@fencepost.gnu.org> (raw)
In-Reply-To: <AANLkTin+0ozrOsXDQX7AgzqwokNCF3-P8443kLM2HrnT@mail.gmail.com> (message from Kai Tietz on Thu, 3 Mar 2011 13:50:40 +0100)
> Date: Thu, 3 Mar 2011 13:50:40 +0100
> From: Kai Tietz <ktietz70@googlemail.com>
> Cc: gdb@sourceware.org
>
> hmm, I admit that it is pretty unlikely that *nix-nat parts are used
> with DOS-style paths. Nevertheless on cross-compiling from windows to
> *nix such paths can happen easily.
How can this happen, even for cross compilation? Can you describe a
use-case?
> Additionally it is IMHO also an issue of consistance in source.
There's no need for consistency here. Someone who reads a
BSD-specific or Linux-specific source file should already know that
backslashes are not directory separators there.
next prev parent reply other threads:[~2011-03-03 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=QoOiBg3XmMv+hRNe8DkT2YiVGZ=7NhaQwzCey@mail.gmail.com>
2011-03-03 12:02 ` Kai Tietz
2011-03-03 12:15 ` Mark Kettenis
2011-03-03 12:50 ` Kai Tietz
2011-03-03 13:13 ` Eli Zaretskii [this message]
2011-03-03 13:21 ` Kai Tietz
2011-03-03 13:43 ` Andreas Schwab
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=E1Pv8LY-0005tI-7d@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=ktietz70@googlemail.com \
--cc=mark.kettenis@xs4all.nl \
/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