[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

SVN status indicating a file is modified when it's not.

From: Bill Williams <billwilliams_at_qcsoftware.com>
Date: 2006-03-28 21:03:03 CEST

I think maybe I've found a bug with the windows version of subversion.

We are using SVN 1.3.0 with svnserve giving us access to the repository.

We have a mixed environment. Our server is linux and our workstations
are windows accessing the linux server via samba. When I first created
the various workspaces, I checked everything out under linux. All
source code files and makefiles have the eol-style set to native;
therefore, all of files are in unix format with the lines ended with a
newline character.

Since the initial checkout, changes have been made to both source code
and makefiles. These changes are usually performed under windows and
committed to the repository via Tortoise.

I will then update my particular workspace using Tortoise and this is
where the problem now appears. Under linux, an "svn status" command
shows no modifications which is correct. But under Windows, it will say
the makefile has been modified. It does this with both the "svn status"
command and Tortoise. I looked at the files that were changed and I
have found the newly updated source files and makefiles are now in a DOS
format with CR/LF on the end of the lines; however, the base files in
the .svn/text-base directory are all still in a unix format. What I
find interesting here is the source files do not show that they have
been modified, only the makefiles when this occurs.

Has anyone seen this behavior before?

Thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 28 21:05:32 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.