Michael Livshin wrote:
> > For anyone not familiar with the term (what're you doing on the SVN
> > list then?)
> stalking. why?
> [ oops ;) ]
Yeah, I should've put a smiley at the end of that paren. Sorry.
> > I hate sticky tags, they stick to the wrong places.
> you mean they stick to individual files but should stick to
> hierarchies instead?
Something like that. For instance, right now we import APR into the
SVN tree, but it doesn't happen magically -- you have to do the checkout
by hand. Sooner or later, APR will have a stable release, tagged in the
APR repo, and we may decide to use only stable releases of APR in SVN.
So the checkout instructions for APR will change to include the correct
tag, and whoever does a `cvs update -A' from the top of the tree gets
what they deserve. Obviously, that's not a stable situation.
If instead the fact that SVN is using APR revision 'foo' were a property
of the 'apr' subdir of the SVN tree, that wouldn't be a problem, and
sticky tags could probably go away completely.
CVS's notion of alias modules is almost equivalent to configurations,
except that you can't specify the version (tag) and repository of each
Oh yes -- configurations can be embedded anywhere in the tree, like
directories; and their contents should be version-controlled, of course.
home: <brane_at_xbc.nu> http://www.xbc.nu/brane/
ACM: <brane_at_acm.org> http://www.acm.org/
Received on Sat Oct 21 14:36:12 2006