On Mon, Mar 22, 2004 at 11:17:42PM -0500, Glenn Maynard wrote:
> On Mon, Mar 22, 2004 at 09:32:26PM -0600, Ben Collins-Sussman wrote:
> > >A property roughly saying "don't keep history" would be extremely useful,
> > >and self-maintaining. I simply don't want versioning for certain files.
> >
> > Then why put them in a version control system? :-)
>
> It's our main repository of files. Versioning is important for many of the
> files, but other functions are important for all files: distributing data to
> everyone working on the project, and keeping everyone up to date with
> everyone else, which are things CVS and SVN are both very good at.
But did you consider how your proposition would work out:
a) svn works on filesets, not files.
b) all repositories start out empty at r0.
Now consider:
r0: start
r50: mkdir /path/to/bigfiles
r100: add /path/to/bigfiles/nohistory
r110: change /path/to/bigfiles/nohistory
Now you do not want nohistory to store history information ;)
Ok, answer the following questions:
1) What to do with with svn -r 100 repopath?
That one is easy, so I try to answer it: Just give r110 version of nohistory
2) What about revision 20? I mean the directory where nohistory is stored
doesn't even exist.
Andreas
>
> --
> Glenn Maynard
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 25 10:27:43 2004