This is the mail archive of the
cygwin-patches@cygwin.com
mailing list for the Cygwin project.
Re: [Patch] cygcheck: warn about empty path-components
Op Wed, 6 Oct 2004 22:15:58 -0400 schreef Christopher Faylor
in <20041007021558.GL2722@trixie.casa.cgf.cx>:
: On Thu, Oct 07, 2004 at 04:05:14AM +0200, Bas van Gompel wrote:
[...]
: > s/-v/-h/. (I'm waiting for the other (trailing slash) patch to be
: > applied or rejected, before submitting this.)
:
: I missed the part about the warning before but I *really* don't think we
: need to warn the user about standard UNIX behavior in cygcheck. That is
: really not what's for.
It's for diagnosing problems with the cygwin-environment, isn't it?
The (to be) warned about condition is on the edge of windows and cygwin.
No windows or UNIX utility is going to warn about it.
[...]
: > : Why are we bothering with this?
: >
: > If I may attempt to answer this one... Many people may not know of
: > this usage, yet may have their windows path ending on a ';'.
:
: I'm sure the same thing is true on UNIX and yet it has survived for
: years without a unicheck program informing people of this fact.
There are no windows paths in UNIX, and there is no unicheck program
for any purpose. Does this mean cygcheck should be removed?
What are you planning to do? Will you revert this patch, reject the
next patch and leave things as they are, or consider it when it's
submitted?
L8r,
Buzz.
--
) | | ---/ ---/ Yes, this | This message consists of true | I do not
-- | | / / really is | and false bits entirely. | mail for
) | | / / a 72 by 4 +-------------------------------+ any1 but
-- \--| /--- /--- .sigfile. | |perl -pe "s.u(z)\1.as." | me. 4^re