Bug 3561 - bookmark update are not pushed to successors.
Summary: bookmark update are not pushed to successors.
Status: RESOLVED FIXED
Alias: None
Product: Mercurial
Classification: Unclassified
Component: Mercurial (show other bugs)
Version: unspecified
Hardware: PC Linux
: normal bug
Assignee: Bugzilla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-30 06:49 UTC by Pierre-Yves David
Modified: 2012-10-19 14:24 UTC (History)
2 users (show)

See Also:
Python Version: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre-Yves David 2012-07-30 06:49 UTC
When you push the successors of a formely bookmarked changeset, the bookmark is not properly updated remotely because the successors is not a descendants of the precursors.

The bookmark code which decide to update bookmark should take obsolete relation into account.
Comment 1 HG Bot 2012-09-17 17:10 UTC
Fixed by http://selenic.com/repo/hg/rev/a7b3fdaf768d
Pierre-Yves David <pierre-yves.david@logilab.fr>
bookmark: take successors into account when updating (issue3561)

When we rewrite a bookmarked changeset, we want to update the
bookmark on its successors. But the successors are not descendants
of its precursor (by definition). This changeset alters the bookmarks
logic to update bookmark location if the newer location is a successor
of the old one[1].

note: valid destinations are in fact any kind of successors of any kind
      of descendants (recursively.)

This changeset requires the enabling of the obsolete feature in
some bookmark tests.

(please test the fix)