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

Re: Files in repository but not version controlled

From: Bastiaan Veelo <Bastiaan.N.Veelo_at_ntnu.no>
Date: 2006-09-22 12:31:47 CEST

Talden wrote:
> What happens when you checkout an earlier revision? You get a file
> that is dated dramatically in the future whose content may not be
> relevent to the checked out version.

I think what should happen when you check out an earlier revision is
that the hosted files should not be there. Like they never existed in
that revision. So you would not get future dated files in a checkout. I
think that the ability to evaluate generated files without even a
working copy is most valuable for the HEAD revision only. If it would
not, you could just "svn add" them.
If you check out an earlier revision it is usually to track down the
cause of a problem. If you need generated files that relate to that
revision, you can generate them in the working copy.

> I'd like to see the use-case that makes this facility valuable before
> a feature that seems to be nothing more than a server filesystem added
> to Subversion.

The use case is to serve generated files of the HEAD revision only that
typically work without the need for a working copy (like HTML) in a
convenient way for readers and writers alike. It is a convenience,
nothing more.

> Can anyone provide a concise example of a mixed
> environment where some files should appear the same regardless of the
> working-copy revision? It does seem as though externals might be able
> to do what's needed instead.

I am not interested in a working copy where files appear the same
regardless the revision.

Best regards,

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 22 13:06:14 2006

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