Bookmarks in core?

David Soria Parra dsp at php.net
Mon Nov 29 17:15:34 CST 2010


On 2010-11-29, Brodie Rao <brodie at bitheap.org> wrote:
> On Nov 30, 2010, at 6:07 AM, Matt Mackall wrote:
>
>> Discuss.
>
> Some thoughts:
>
> - I think the track.current option is confusing. Why not enable it by  
> default?
Two reasons. (1) backward compatibility. The first implementation fo bookmarks
didn't have this flag. If we enable it, we can confuse people that use bookmarks
without that option. (2) track.current is a way to emulate git's branch behavior.
This is a 'naming for a head'. The name bookmarks suggests that you can use it
like the bookmarks you would put into a book. If you go to the next page you probably
will advance both bookmarks and not just one. Therefore the default beahvior is more
related to the naming of the feature.

> - This might be a secondary topic, but I think it'd be great to have  
> remote-tracking bookmarks. I.e., each entry in hg paths gets a  
> bookmark, and pulling from a repo moves that bookmark forward. I think  
> it'd be great to have this on by default; it would make it easier to  
> deal with (or put off) merges involving large numbers of changesets,  
> since you could easily identify what head each repo is at.
I would like to see that too.



More information about the Mercurial-devel mailing list