[Bug 6902] New: Identify and/or control obsmarkers in push
mercurial-bugs at mercurial-scm.org
mercurial-bugs at mercurial-scm.org
Wed Aug 21 22:08:08 UTC 2024
https://bz.mercurial-scm.org/show_bug.cgi?id=6902
Bug ID: 6902
Summary: Identify and/or control obsmarkers in push
Product: Mercurial
Version: 6.7.4
Hardware: PC
OS: NetBSD
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: evolution
Assignee: bugzilla at mercurial-scm.org
Reporter: mercurial-bugzilla at campbell.mumble.net
CC: mercurial-devel at mercurial-scm.org,
pierre-yves.david at ens-lyon.org
Python Version: ---
I have a topic whose changesets have been obsoleted by non-topic changesets.
(This arises from working in a topic on the hg side of NetBSD's cvs->hg
conversion, and then committing to cvs, and then obsoleting the changesets on
the topic once they appear in the conversion. The context isn't particularly
important but it may help to understand how this happens.)
If I do `hg outgoing -r "topic(mytopic)"', it fails because there's no
non-hidden changesets on that topic.
> abort: specified revisions evaluate to an empty set
> (use different revision arguments)
If I do `hg outgoing --hidden -r "topic(mytopic)"', it doesn't fail but it
doesn't do anything because the changesets are already pushed.
> searching for changes
> no changes found
If I use `hg log --hidden -r "topic(mytopic)"' on the remote end to find the
head that is supposed to be obsolete, say 6577d883cf09, and do `hg outgoing
--hidden -r 6577d883cf09', it still says:
> searching for changes
> no changes found
And hg push doesn't seem to have any effect.
If I use `hg log --hidden -r "allsuccessors(topic(mytopic)) & public()"' to
find the public successor's changeset id, say 3b19e2321332, and do `hg outgoing
--hidden -r 3b19e2321332', it still says:
> searching for changes
> no changes found
And hg push doesn't seem to have any effect.
1. How do I tell what obsmarkers will be pushed, like hg outgoing will tell me
which changesets will be pushed?
2. How do I choose which obsmarkers to push, like pushing a particular
obsmarker for a particular changeset?
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list