Bookmarks in core?

Brodie Rao brodie at bitheap.org
Tue Nov 30 16:29:44 CST 2010


On Nov 30, 2010, at 10:07 AM, Brodie Rao wrote:

> On Nov 30, 2010, at 6:07 AM, Matt Mackall wrote:
>
>> Discuss.
>
> Some thoughts:
>
> - If we integrate them in core, I'd like to see integration with the  
> branch command. E.g., hg branch --bookmark. I think that would make  
> it easier for people to discover bookmarks and know that they're  
> related to branches. On the other hand, I guess they don't  
> necessarily have to be used like branches, so that might not be the  
> best idea.
>
> - They're kind of annoying to use over the network. I don't like  
> having to use the -B flag to manually specify what bookmarks I want  
> to push. I've also noticed an issue with push -B where it forgets  
> HTTP credentials from the normal push process, so sometimes you'll  
> be asked to log in twice.
>
> - I think the track.current option is confusing. Why not enable it  
> by default?
>
> - 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.

Some additions:

- We should probably move bookmarks out of the tags namespace and  
provide a proper public method for them on the repo object.

- We should have hooks for pushkey.


More information about the Mercurial-devel mailing list