[Bug 5352] New: Auto-Rebase on Pull makes tags on unpushed changesets invalid
bugzilla at mercurial-scm.org
bugzilla at mercurial-scm.org
Mon Aug 29 12:00:40 UTC 2016
https://bz.mercurial-scm.org/show_bug.cgi?id=5352
Bug ID: 5352
Summary: Auto-Rebase on Pull makes tags on unpushed changesets
invalid
Product: Mercurial
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: rebase
Assignee: bugzilla at selenic.com
Reporter: mubed at yahoo.com
CC: mercurial-devel at selenic.com
I know that this is by design that a tag tags a fixed changeset hash and
rebasing changes the changeset hashes, so you could say this is not a bug.
BUT I believe the usecase exists and is very popular that someone works offline
for a while and tags some special commits to find them later, then he tries to
push his changes and sees that others have changed the code, so he pulls first
and has auto-rebase on. This results in a clean rebase and his changes are at
the top of the changes others did, but the tags point to dead changesets now
and are practically invalidated without any warning.
I suggest that THG checks on rebasing if any tags are getting invalid and give
the user one of these choices:
1.Update tags (should be default, because the most common case)
2.Remove invalid tags
3.Abort rebase and merge instead
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list