Yitzchak Scott-Thoennes wrote:
> This part does sound like a bug. Perhaps this diff optimization
> should be suppressed, since in cases like this, ./a and .\a have
> effectively different content.
If anything, you would want to just add a test to the stat-comparison
code to check that both files
On Sat, Mar 05, 2005 at 09:52:16PM -0500, Igor Pechtchanski wrote:
> On Sun, 6 Mar 2005, Arend-Jan Westhoff wrote:
> > It also seems inconsequent if what you say is truely correct and what is
> > intended that when I use my file 'a' from my original example and do the
> > following:
> > copy a
On Sat, Mar 05, 2005 at 06:55:12PM -0800, Brian Dessent wrote:
> Arend-Jan Westhoff wrote:
>
> > It also seems inconsequent if what you say is truely correct and what is
> > intended that when I use my file 'a' from my original example and do the
> > following:
> > copy a b
> > that then:
On Sat, Mar 05, 2005 at 06:55:12PM -0800, Brian Dessent wrote:
>I don't know enough about Cygwin history or internals to say why this is
>the case. Someone who knows more about it would have to explain it.
>And as you've seen it can lead to confusing situations.
I'm not sure how an explanation w
On Sun, 6 Mar 2005, Arend-Jan Westhoff wrote:
> Thanks for the explanation. However I don't quite understand this is
> what one would want.
I'll let someone else address most of your points except one:
> It also seems inconsequent if what you say is truely correct and what is
> intended that whe
Arend-Jan Westhoff wrote:
> It also seems inconsequent if what you say is truely correct and what is
> intended that when I use my file 'a' from my original example and do the
> following:
> copy a b
> that then:
> diff ./a .\b
> says that the files are completely different, wherea
Thanks for the explanation. However I don't quite understand this is what one
would want.
With regard to paths I would expect one to want:
A Windows or Posix style path is converted to one internal path format.
After this conversion the behaviour is independent of whatever the
original format was
[EMAIL PROTECTED] wrote:
> Have attached a cygcheck, though I am afraid it's rather large.
As suspected, you have textmode mounts -- see Igor's response which was
spot on. To summarize, using '\' as a path seperator bypasses all of
Cygwin's processing since it signals a native windows path/filen
Brian Dessent wrote:
>Arend-Jan Westhoff wrote:
>>
>> Noticed that when diff is run with two differing files,
>> one with and one without a directory specifier:
>> diff a someDir\b
>> then all lines are reported as different.
>> Whereas when both have a directory specifier:
>> diff
On Fri, 4 Mar 2005, Igor Pechtchanski wrote:
> On Fri, 4 Mar 2005, Brian Dessent wrote:
>
> > I cannot reproduce this, either from a bash prompt or from cmd using
> > your .bat file:
>
> I can reproduce this (even under bash). All you need is a textmode mount
> and files with CRLF line endings.
On Fri, 4 Mar 2005, Brian Dessent wrote:
> Arend-Jan Westhoff wrote:
> >
> > Noticed that when diff is run with two differing files,
> > one with and one without a directory specifier:
> > diff a someDir\b
> > then all lines are reported as different.
> > Whereas when both have a directory
Arend-Jan Westhoff wrote:
>
> Noticed that when diff is run with two differing files,
> one with and one without a directory specifier:
> diff a someDir\b
> then all lines are reported as different.
> Whereas when both have a directory specifier:
> diff .\a someDir\b
> output is no
Noticed that when diff is run with two differing files,
one with and one without a directory specifier:
diff a someDir\b
then all lines are reported as different.
Whereas when both have a directory specifier:
diff .\a someDir\b
output is normal.
(Filenames, argument order or using -
13 matches
Mail list logo
