RE: Revision # theorhetical upper limit
From: <andy.glew_at_amd.com>
Date: 2004-05-20 15:48:25 CEST
> andy.glew@amd.com wrote:
Reid Spencer [reid@x10sys.com]
As I mentioned earlier, I started writing a longer reply,
Briefly:
Branching in CVS is easy because it does not
This applies particular to incomplete branches
E.g. with repository
However, you can easily check out the mixed
In particular, it is easy to do so for & modules.
With Subversion, on the other hand,
(a) if you branch all of the repository things
(b) it is easy to create a mixed workspace
(c) but it is hard to tell someone else how to
Similarly, with Subversion, TTBOMK, svn:external
If I have
When I branch module1, I feel obliged to test this
But since the svn:external contains absolute paths,
--- Getting back to Reid's point: it is not my Makefiles that contain absolute paths. It is svn:externals that contains the absolute paths. Either these absolute paths must be edited by hand, or, I can use Makefile magic to patch it over. But I have still not found a really painless way. --- Meta-comments: SubVersion branching works best if you branch *everything* that might possibly need to be built with the branch. (But this leads to constant merge tracking.) SubVersion branching does not work so well, so far as I have been able to figure out, when you only want to branch a submodule. Subversion does not make it easy to copy overlaid or mixed contous, e.g. HEAD + a branch, through the repository. SubVersion uses too many absolute URLs, e.g. in svn:externals. As Reid commened about Makefiles, absolute pathnames of any form create position dependent configurations. --- Hmmm..... this was about all I wanted to say. Maybe I won't send the interrupted email. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.orgReceived on Thu May 20 15:49:53 2004 |
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.