Re[2]: subversion

> Because it was Hard to do. In CVS, the CVS/Entries file is just
> tracking a bunch of independent files with separate RCS revision
> numbers. Files can come and go from that Entries list, and CVS just
> doesn't care... why? Because it's not versioning directories. CVS
> has no idea what things are supposed to be in the directory or not...
> it's mostly a wrapper around RCS.

> Because Subversion is versioning directories, things get a lot more
> complex. The "basic unit" of version control is a directory, and in
> the interest of releasing Subversion 1.0 before the sun engulfs the
> solar system, we had to choose our battles carefully. :-)

> That said, a developer is working on a feature to make 'svn checkout -
> N' actually work as expected. There will probably be a new UI to
> explicitly include/exclude children that you want or don't want, and
> the "checkout a single file" feature will very likely fall out of
> this as a sub-case.

Glad to hear that :)

By the way I got the impression this can take months or years to be done. Just got the idea... isn't it possible to add svn cat to the directory properties... i.e.:
svn:cat \\path\to\file.c

This way the folder will be checked out along with the "single file" in question. Yeah, it'll not be versioned, but since this issue mostly involves using external files (headers files, common files, etc). It may solve most of the problems?
Received on Wed Aug 31 15:31:43 2005