[PATCH v2] bookmarks: pull new bookmarks from remote by default

[Kevin Bullock]

On May 16, 2012, at 6:53 AM, Martin Geisler wrote:

> Pierre-Yves David <pierre-yves.david at logilab.fr> writes:
> 
>> On Wed, May 16, 2012 at 12:13:08PM +0200, Martin Geisler wrote:
>>> In other words, Kevin should mark changesets secret before running 'hg
>>> serve' if he doesn't want people to get when when they pull/clone.
>>> Bookmarks on such secret changesets will then also stay in place. That
>>> seems consistent and not too inconvenient to me.
>> 
>> Does not solve the case where I have a <private> bookmark in a the
>> middle of my draft history.
> 
> I haven't used bookmarks much, but I would be okay with saying that this
> just isn't possible -- maybe the draft history above should really be
> secret? Why would you share the history without sharing the bookmarks?
> If the bookmarks are pointing to heads (as they should), then they will
> be useful in other repositories as well. If they don't point to heads,
> could you have used a local tag instead?
> 
> Making a simple rule feels important to me: the above rule is that
> exposing a changeset also exposes the bookmarks that point to it.

I agree with this assessment. I just brought it up to make sure the rationale for the change was explained and preserved in writing. :)

pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
Kevin R. Bullock

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20120516/6f3d5bed/attachment.html>