From: Charles Wilson <cwilson@ece.gatech.edu>
To: Heitzso <heitzso@home.com>
Cc: cygwin@cygwin.com
Subject: Re: more info on cvs
Date: Mon, 30 Apr 2001 12:45:00 -0000 [thread overview]
Message-ID: <3AEDC190.9D040061@ece.gatech.edu> (raw)
In-Reply-To: <3AEDAF0F.80309@home.com>
Technically, I think the cvs protocol itself expects that paths are
specified using backslash. However, certain implementations/ports of
cvs to native windows have relaxed that, so that Windows users can use
"normal" backslashes when specifying pathnames. Then, netbeans/forte
took that laxness as license (or perhaps the developers at Sun just
said, "Hey, windows -- paths have backslashes -- okay, we'll do that
too")
What we're left with is this: we can either (a) limit pathnames to using
only '/' as specified by the spec (which also, BTW, explicitly *allows*
'\' as a normal char in a filename !!!), or (b) violate the spec and
adapt cvs on cygwin to explicitly convert '\' to '/' every time.
The problem is, some remote system to which your local cygwin-cvs client
talks, might have a file with a *legal* name containing '\'. What do we
do then?
I'm in favor of (b), and treat the "problem" above as another
windows-ism (like the fact that "aux" is an illegal name on windows but
is FINE everywhere else on the planet...)
--Chuck
P.S. Sorry for being slow to respond, Heitzso, but I've been very busy
with (a) my job (b) cygwin release 1.3.0^H1, (c) ncurses release 5.2-5
lately. :-) I "maintain" about 20 packages and it's getting to be
pretty overwhelming...
Heitzso wrote:
>
> After reading FAQ/Doc I'm noting that goal of Cygwin is
> for all programs to run under cmd.exe with backslashed file names
> just fine.
>
> I assume that cvs code needs a patch to convert
> backslashed names to forward slashes or to
> change the test in last_component() to find
> backward as well as forward slashes.
>
> Note I'm not the cvs cygwin maintainer.
> I emailed the maintainer awhile ago
> and haven't heard back.
>
> Should I go into cvs tree and dig out
> cvs patch code and get setup to alter
> the cvs cygwin patch?
>
> Thanks,
> Heitzso
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2001-04-30 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 10:43 sshd on win2k [revisit] Harry Putnam
2001-04-30 11:34 ` more info on cvs Heitzso
2001-04-30 12:45 ` Charles Wilson [this message]
2001-04-30 13:49 ` Christopher Faylor
2001-04-30 15:17 ` Charles Wilson
2001-04-30 13:07 ` Christopher Faylor
2001-04-30 12:06 ` sshd on win2k [revisit] Dmitrii Pasechnik
2001-04-30 13:07 ` Charles Wilson
2001-05-02 6:22 ` Corinna Vinschen
2001-05-02 6:58 ` Michael Erdely
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=3AEDC190.9D040061@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.com \
--cc=heitzso@home.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).