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

RE: Why does svn want to write files to .svn/tmp for read-only operations?

From: Paul Koning <pkoning_at_equallogic.com>
Date: 2006-01-09 22:20:14 CET

>>>>> "Lieven" == Lieven Govaerts <lgo@mobsol.be> writes:

 Lieven> Paul, When you do svn diff, you ask SVN to show the
 Lieven> differences between your file and the base version of your
 Lieven> file ( stored in .svn/text-base ).

 Lieven> Before that base file is ready to be compared, some
 Lieven> translations have to be done first. For instance, the CR/LF
 Lieven> translation is done based on your environment, keywords are
 Lieven> expanded etc. The translated file is stored in the .svn/tmp
 Lieven> folder and that one is used to compare with your version.

It's puzzling that this isn't done with pipes, or with in-memory
processing. With an external diff, I suppose you might need one temp
file (though not two) but the internal diff engine should do all this
on the fly.

On the other hand, none of that explains why a temp file is created
for a status command. Quite apart from being a nuisance when people
don't have write access to the working directory, I would expect that
an in-memory solution would be a whole lot faster, since it doesn't
have to create, write, read, and delete temp files all over the place.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 9 23:38:02 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.