I have done a checkout to Windows and one to Linux and
my results show that the text base files always have CR-LF
in them. This differs from what you suggest here. I did
a svn status on Linux and it shows no modifications as it
should on a fresh untouched working copy. A check of files
in the working copy shows that they have the correct eol,
that is, a LF for each line.
I have to disagree on the effect of less. Something is changing
the files when mounted via smbfs and less or some other file acces
is used. svn diff then claims that the file has only line feeds as the eol
character. A check of the file with a hex editor clearly shows that
the CR-LF is really there. Thus I can only conclude that something in
the system info for each file is changed so that svn diff and svn status
treat the file like it is from Linux instead of MS Windows.
Delbert
On Wednesday 19 November 2003 14:51, you wrote:
> Delbert D. Franz wrote:
> >1.Info-zip's zip and unzip must change some aspect of the
> >file information that causes svn to think the file is a Linux
> >file. However, this change is hidden from the ordinary
> >user.
>
> Have you looked at the text base files? I bet info-zip changes them to
> CRLF line endings, whereas with svn:eol-style=native, all the text bases
> should use plain LF.
>
> >2. Mounting a shared drive on W2K in Linux using smbfs
> >and then accessing the file with an editor or the less
> >command does the same thing,
>
> I can't believe 'less' changes the files in any way. It might change the
> last-accessed time, though, and that _might_ break the date-baed
> comparison. Is it possible that pkzip also modifies the text bases but
> preserves the timestamps?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 20 06:23:17 2003