This is a follow-up patch to 5162753c4c14. This makes unshelve
stores the information about interactive mode on conflicts.
Details
- Reviewers
pulkit - Group Reviewers
hg-reviewers - Commits
- rHGee86ad6f50fe: unshelve: store information about interactive mode in shelvedstate
Diff Detail
- Repository
- rHG Mercurial
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
mercurial/shelve.py | ||
---|---|---|
181 | We are already in shelve code, so no need to prepend shelved to the name. Also, we can only had interactive stored in the shelved state. If it's not present in the state file, we can assume we were not running interactive unshelve. | |
856 | unrequired change. | |
945 | This change is unrelated to storing info about interactive in shelvedstate. Can you decouple this into a separate patch? |
mercurial/shelve.py | ||
---|---|---|
945 | Doing that right away! |
mercurial/shelve.py | ||
---|---|---|
181 | The above comment is not done. I meant, we don't need _noninteractive. |
mercurial/shelve.py | ||
---|---|---|
181 | Done. |
@@ -936,7 +942,7 @@
if opts.get("name"): shelved.append(opts["name"])
- if abortf or continuef and not interactive:
+ if abortf or continuef:
mercurial/shelve.py:938: local variable 'interactive' is assigned to but never used
Maybe --continue --interactive has to be banned if the mode can't be
overridden by the command option.
mercurial/shelve.py:938: local variable 'interactive' is assigned to but never used
Maybe --continue --interactive has to be banned if the mode can't be
overridden by the command option.
Noted. Created D6703. Thanks!
We are already in shelve code, so no need to prepend shelved to the name.
Also, we can only had interactive stored in the shelved state. If it's not present in the state file, we can assume we were not running interactive unshelve.