In D9843#149037, @marmoute wrote:

In D9843#149035, @mharbison72 wrote:

Can we get space for extra flags for things not supported by the filesystem? I'm thinking specifically +x and symlink support on Windows.
https://www.mercurial-scm.org/wiki/DirState#Proposed_extensions

That would be a dirstate thing, not a revlog thing, right ?

Can we get space for extra flags for things not supported by the filesystem? I'm thinking specifically +x and symlink support on Windows.

Big picture, why do we need to be able to tell namespace parts from command parts?

To make sure the user understand they are stepping in an entire different realm with different rules.
In the standard namespace (no prefix) we garantee (or aims at) the lack of footgun and excellent backward compatibility.
The debug namespace should not be somewhere any normal user ever have to go (at least without a responsible staff member)
The admin namespace will have its own rules and its own "be careful, this is not a "normal" situation to be there.
So we want something more distincting than just a simple - that we could have for "command group" or readability like phab-send, phab-read, etc.

In D9836#148957, @marmoute wrote:

Should this go on stable instead to make the test fixed on stable too?

In D9832#148844, @martinvonz wrote:

In D9832#148843, @mharbison72 wrote:

Was its purpose to be used in the tests? (It probably should have been put there in that case, but maybe importing mdiff there is more complicated?)

I'm not sure I follow. Do you mean that the test conditions that I removed in this patch might be worth keeping the function for? I had assumed that the function existed because it was used somewhere in Bazaar, but I didn't check if it actually was.

Was its purpose to be used in the tests? (It probably should have been put there in that case, but maybe importing mdiff there is more complicated?)

Is this one obsoleted by D9785, D9786 (and friends)?

Queued with some minor copyediting, thanks

The source of the failure was amended in place.

make -C .. local PYTHON="py -3.9" on Windows was enough to trigger if for me all the time.

In D9472#143491, @martinvonz wrote:

In D9472#143442, @Alphare wrote:

I'm honored to be the mojibake test. ;)

:)
@mharbison72: I'm not doing anything more with this test. Are you or should I drop this patch? I'll at least mark it "Plan Changes" for now.

I get test failures with this:

In D9677#146367, @pulkit wrote:

In D9677#146243, @marmoute wrote:

As pointed in a pa previous comment, this is problematic, because this does not preserve the same consistency as the previous code

While the copy consistency can be maintained here, future changes (WIP) will break the consistency more. In upcoming work, we want to only touch parts of repository which needs to be updated. This will lead us to do selectively moving data from the upgraded repository to the current one.

Oops, typo on my end with phabupdate. I still wanted to flag the new return statement.