[Bug 6906] New: Quarantined hg import or hg pull

Александр Литягин alexraynepe196 at gmail.com
Mon Aug 26 06:47:47 UTC 2024


Meybe change a phase of your changesets to `secret` state can help you?

On 24.08.2024 3:02, mercurial-bugs at mercurial-scm.org wrote:
> https://bz.mercurial-scm.org/show_bug.cgi?id=6906
>
>              Bug ID: 6906
>             Summary: Quarantined hg import or hg pull
>             Product: Mercurial
>             Version: 6.7.4
>            Hardware: PC
>                  OS: NetBSD
>              Status: UNCONFIRMED
>            Severity: feature
>            Priority: wish
>           Component: Mercurial
>            Assignee: bugzilla at mercurial-scm.org
>            Reporter: mercurial-bugzilla at campbell.mumble.net
>                  CC: mercurial-devel at mercurial-scm.org
>      Python Version: ---
>
> Suppose I receive a changeset series from hg export, or a bundle, or a topic in
> a remote repository, and I want to review it, play with it, build from it,
> check out the tree at the point of individual changesets in it, and so on.  But
> I don't want to push changesets in it, or include them in clones of my
> repository, or keep the changesets around at all -- I may want to nix it all
> after review: maybe it doesn't pass review, maybe it adds confusing extra heads
> to branches, maybe it has tainted content, maybe it has a giant binary file by
> accident.
>
> Is there a way to quarantine these changes so that their impact on state in my
> repository is limited and I can easily strip them all later?
>
> I know _if_ I can identify all of the changesets in question, I can use `hg
> strip' to nix them.  But is there a way to guarantee that I can later identify
> all changesets which are new from this hg import or hg pull?  Can I, say, put
> some kind of (local) tag on them when I import or pull, so that I can get a
> revset of that tag later?
>
> For example, in git, I could create a remote, and use `git ls-remote' or even
> `git remote update' or `git fetch <remote>' and then delete the remote later
> (and `git gc' the objects away).
>



More information about the Mercurial-devel mailing list