https://bz.mercurial-scm.org/show_bug.cgi?id=6275
Bug ID: 6275
Summary: Spurious warnings about obsolete markers with obsolete
feature disabled on `hg incoming`
Product: Mercurial
Version: 5.3
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: bug
Priority: wish
Component: Mercurial
Assignee: bugzi...@mercurial-scm.org
Reporter: matt_harbi...@yahoo.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---
Using a clone of hg-committed:
$ ../hg.exe in
comparing with https://www.mercurial-scm.org/repo/hg-committed
searching for changes
obsolete feature not enabled but 214101 markers found!
changeset: 45612:088ab52a04bc
user: Martin von Zweigbergk <martinv...@google.com>
date: Thu Feb 13 13:41:45 2020 -0800
obsolete: pruned using prune by Martin von Zweigbergk
<martinv...@google.com>
summary: debugmergestate: make templated
changeset: 45669:2527c10a2569
branch: stable
parent: 45663:b339faf3f843
user: Kyle Lippincott <spect...@google.com>
date: Thu Feb 20 17:06:01 2020 -0800
summary: shelve: add test clearly demonstrating that the conflict labels
are backwards
changeset: 45670:69b091cdc506
branch: stable
tag: tip
user: Kyle Lippincott <spect...@google.com>
date: Thu Feb 20 16:21:00 2020 -0800
summary: shelve: fix ordering of merge labels
I bisected it back to evolve 2db0aca03a88 (using hg 5.0, because of
incompatible hg changes afterward). I put enough printing in to see that the
main repo sees the `experimental.evolution=all` config set by the evolve
extension, but the bundlerepo created to process the bundle grabbed on incoming
doesn't.
If `--config experimental.evolution=all` is set on the command line or the user
config file, the warning doesn't occur. So it's not hard to work around this,
but the fact that configs aren't being applied is concerning.
--
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
