![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I officially hate SVN.
(Don't get me wrong; it's probably great for power users and people who never merge to/from a branch more than once or twice. Many thanks to![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-syndicated.gif)
preedmozblog, by the way, for pointing me at a tool that might replace my entire whiteboard for branch merge management. The problem I have with SVN is that when not everyone is a power user, or not everyone knows to track merges on their whiteboard, you get real trouble.)
(Don't get me wrong; it's probably great for power users and people who never merge to/from a branch more than once or twice. Many thanks to
preedmozblog, by the way, for pointing me at a tool that might replace my entire whiteboard for branch merge management. The problem I have with SVN is that when not everyone is a power user, or not everyone knows to track merges on their whiteboard, you get real trouble.)
no subject
1) "What branches/tags were made after this patch?" (Which probably should really be, "Which branches/tags include this patch, either by branching after it was checked in, or by merging it in?")
2) "Did branch X include this patch?"
You can go through the logs of the branch(es) and trunk and figure them out (well, maybe not which branches got a patch applied later, unless you set up some careful conventions regarding log messages), but with CVS, you could look at the version numbers for the branches and tags right in the same log.