https://bz.mercurial-scm.org/show_bug.cgi?id=5619
Bug ID: 5619
Summary: obsmarker pushed for prune even though changeset was
not pushed
Product: Mercurial
Version: default branch
Hardware: PC
OS: Linux
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: evolution
Assignee: bugzi...@mercurial-scm.org
Reporter: martinv...@google.com
CC: mercurial-devel@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
This is what happened:
Repo1 (my repo):
1. Create 4 patches
2. Send for review
Repo2 (Yuya's repo)
1. "hg import --obsolete" the 4 patches
2. Rebase patch 4 onto patch 4
3. Rebase patch 3 onto 4 (i.e. steps 2 and 3 make patch 3 and 4 switch place)
4. Push patches 1,2,4 to repo3
I then pulled from repo3 into repo1 and my local patch 3 was obsoleted (along
with the expected obsoletion of patches 1,2,4). Since patch 3 was not pushed
from repo2, it feels unexpected that the obsmarker for it got pushed.
(I know why this happens, but it's still very confusing.)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
