[PATCH 2 of 4] clone to master bookmark if available

[Victor Suba]

On Sun, Nov 13, 2011 at 11:12 PM, Arne Babenhauserheide <arne_bab at web.de>wrote:

> Do you mean non-persistent feature branches?
>
> Would it suffice to allow pushing bookmarked heads with an
> --new-bookmarked-heads option (which you could also send permanently and
> which
> would also transfer all bookmarks on the pushed heads)?
>

I think it's more like only consider to transfer a head and it's ancestors
if it has a matching bookmark
on the remote.  And, have a flag to explicitly transfer new bookmark/s to
the remote.

If you're going to have any private feature branches when you try to push
them hg will complain
because you're trying to push new heads on the remote, so the above stops
that.

If we have that then every Mercurial branch needs some "default" bookmark.
 I assumed your idea
for a "master" bookmark was related to that.

Cheers,
Vic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20111113/09e3ce0a/attachment.html>