[Python-Dev] Procedure for sandbox branches in SVN? (original) (raw)

Tim Peters tim.peters at gmail.com
Fri Apr 14 17:19:53 CEST 2006

[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 people disliking branches in CVS can "go away by magic" under SVN:

  1. There's no way to attach a comment to a branch, explaining why it exists. In SVN, that's the checkin comment on the copy command that creates the branch.

  2. Branches are in your face forever after, because the CVS docs strongly warn against trying to use the relevant commands even for tags (let alone branches). The CVS moral equivalent of "svn list repo/branches" keeps growing as a result, and shows up in each cvs log. The ever-growing clutter of long-obsolete info gets depressing <0.5 wink>. The easy possibility in SVN for "out of sight, out of mind" is a huge improvement.

More information about the Python-Dev mailing list