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

RE: What is the .svn/empty-file for?

From: Karan, Cem \(Civ, ARL/CISD\) <CKaran_at_arl.army.mil>
Date: 2005-01-10 17:43:32 CET

> > OK, I can see how there is a portability problem. But as a
> > suggestion, is it possible to put a single empty file in
> the root of
> > the working copy? Or, better yet, put one in the install
> location of
> > subversion itself? That way, all repositories on a machine
> have acess to an emtpy
> > file, without requiring /dev/null to exist/be portable/etc.
> Or am I
> > missing something?
> Only one file in the top of the checkout is not an option,
> because every subdir is a valid checkout by itself. You can
> copy any subdir to a new location and use it as a top dir there.
> Maybe it's worth the change to start using /dev/null or NUL
> now and ditch the .svn/empty files as soon as a major working
> copy change comes by. I'll need to investigate how easy that is.

If you are going to investigate this, are there any other files similar
to the empty files? That is, they are all over the place and they are
constant in some way? If there are, it may be a good idea to come up
with a general solution...

Cem Karan

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 10 17:55:02 2005

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.