Recording branch points

[David Allouche]

John Arbash Meinel wrote:
> Well, I was trying to figure out how you would determine what branch a
> revision was from. But I guess you could just add a revision property of
> 'new_branch => True'.
> And then if that is not present, you assume a revision is in the same
> branch as its left-hand parent.
> And only a new commit in a branched tree would set that.
> 
> And with James's working tree properties patch, it would be moderately
> easy to do so.
> 
> The only problem is that it is a Branch property, and not a WorkingTree
> property. And you can create a new branch without a working tree. In
> fact, I do it all the time:
> 
> bzr branch sftp://public/bzr.dev sftp://public/feature-branch
> bzr checkout sftp://public/feature-branch
> 
> Is (essentially) how I create a new feature branch to hack on. So that
> would mean we want a pending Branch property, which would get removed
> after a commit, but not by pull.

That sounds like a good idea.

I would like if "bzr status" would also report when the "new-branch"
flag is active (for the next commit) and if there was a way to set this
flag manually too. Maybe: "bzr new-branch [yes|no]".

Any idea how bzr could use that information to make users happier, so
they would be an incentive to record meaningful data?

-- 
                                                            -- ddaa

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060920/5d5a9e96/attachment.pgp