RE: Re: Branch root identification -- a (really) simple proposal

I'd say this concept needs to be thought of in the same space as renames and moves, as its concerned with the same fundamental problem - where something came from.

> * helping the client discourage commits of subsets of a branch.

This is not a good thing, if you branch projectA, which contains componentB and C, then its perfectly acceptable to commit B or C by themselves.

> * helping the client warn users about merging at anything less than
> the branch level.

Again, you might want to merge a bugfix from a sub-project as above.

I like the idea of referencing the origin of a branch (and other directories or files) but only for information. Such information *can* then be used to process the data differently, eg, once you know a file was renamed, tree-conflicts start to disappear; once you know a directory is a branch, you can highlight it differently in a UI, but I doubt that we can really use it as more than a hint to the user.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2396020
Received on 2009-09-17 16:23:47 CEST