- User Since
- Jul 16 2017, 3:10 PM (183 w, 3 d)
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.
Tue, Jan 19
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?)
Mon, Jan 18
Queued with some minor copyediting, thanks
Sun, Jan 17
The source of the failure was amended in place.
Sat, Jan 16
Wed, Jan 13
make -C .. local PYTHON="py -3.9" on Windows was enough to trigger if for me all the time.
Tue, Jan 12
I get test failures with this:
Oops, typo on my end with phabupdate. I still wanted to flag the new return statement.