Propagates bookmarks termination

[Pierre-Yves David]

I'm using bookmarks for my Mercurial developpement for a few months. My workflow is as follow:

    At work

     $ hg bookmarks somefeature
     hack hack hack
     $ hg push -B somefeature http://hg-lab.logilab.org/wip/hg/

    at home

     $ hg pull http://hg-lab.logilab.org/wip/hg/
     hack hack hack
     $ hg amend
     $ hg push http://hg-lab.logilab.org/wip/hg/

    eventually

     $ hg patchbomb -r '::somefeature and draft()'

Since 2.3 hg pull synchronize all bookmarks. this part works well !

But when somefeature is queued into core troubles start


  At home

    $ hg pull main
    $ hg bookmark -d somefeature
    $ hg push -B somefeature http://hg-lab.logilab.org/wip/hg/ # to propagate the kill to hg-lab

and from work I need

    $ hg pull http://hg-lab.logilab.org/wip/hg/ -B somefeature

Otherwise an hold version of the bookmarks remains dandling somewhere.

It would be nice if the pull could propagate the deletion of the bookmark the same is does with addition.

I have no plan of how achieve this for now. I just wanted to share this with you.

-- 
Pierre-Yves David

http://www.logilab.fr/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20120920/4bf1ef84/attachment.pgp>