Tim Peters wrote:
Just do it. Branches under SVN are cheap, go fast, and are pretty
easy to work with. Even better, because a branch is just another
named directory in SVN's virtual file system, you can svn remove it
when you're done with it (just like any other directory).
That's all true.
Tim Peters wrote:
Just do it. Branches under SVN are cheap, go fast, and are pretty
easy to work with. Even better, because a branch is just another
named directory in SVN's virtual file system, you can svn remove it
when you're done with it (just like any other directory).
footnote: if
[Martin v. Löwis]
That's all true. Of course, removing the branch won't free up
any disk space - it will just remove the branch from the view
(IOW, it is also easy to bring it back if it was removed mistakenly).
Right! I'm implicitly addressing a different issue, namely that two
reasons for
I'd like to create a branch for maintaining the setuptools 0.6 line through
its beta and final release, while new work proceeds on the trunk for
integration with Python 2.5 and beginning the 0.7 line. Is there any
special procedure I should follow, or can I just make a 'setuptools-0.6'
branch
[Phillip J. Eby]
I'd like to create a branch for maintaining the setuptools 0.6 line through
its beta and final release, while new work proceeds on the trunk for
integration with Python 2.5 and beginning the 0.7 line. Is there any
special procedure I should follow, or can I just make a
