##// END OF EJS Templates
rebase: tweak description of inmemory working even w/ dirty working dir...
rebase: tweak description of inmemory working even w/ dirty working dir One of our users was confused because they read this, and then attempted to run `hg rebase` with a dirty working directory, and it still complained. The reason was that they were attempting to rebase the commit they currently had checked out, which (at least with evolve workflows enabled) involves updating the working directory to be based on the newly rebased commit. Differential Revision: https://phab.mercurial-scm.org/D6507
Kyle Lippincott -
r42640:cda591d2 default
Show More
Name Size Modified Last Commit Author
/ hgext
convert
fastannotate
fsmonitor
highlight
infinitepush
largefiles
lfs
narrow
remotefilelog
zeroconf
__init__.py Loading ...
absorb.py Loading ...
acl.py Loading ...
amend.py Loading ...
automv.py Loading ...
beautifygraph.py Loading ...
blackbox.py Loading ...
bookflow.py Loading ...
bugzilla.py Loading ...
censor.py Loading ...
children.py Loading ...
churn.py Loading ...
clonebundles.py Loading ...
closehead.py Loading ...
commitextras.py Loading ...
eol.py Loading ...
extdiff.py Loading ...
factotum.py Loading ...
fetch.py Loading ...
fix.py Loading ...
githelp.py Loading ...
gpg.py Loading ...
graphlog.py Loading ...
hgk.py Loading ...
histedit.py Loading ...
journal.py Loading ...
keyword.py Loading ...
logtoprocess.py Loading ...
mq.py Loading ...
notify.py Loading ...
pager.py Loading ...
patchbomb.py Loading ...
phabricator.py Loading ...
purge.py Loading ...
rebase.py Loading ...
record.py Loading ...
releasenotes.py Loading ...
relink.py Loading ...
remotenames.py Loading ...
schemes.py Loading ...
share.py Loading ...
shelve.py Loading ...
show.py Loading ...
sparse.py Loading ...
split.py Loading ...
sqlitestore.py Loading ...
strip.py Loading ...
transplant.py Loading ...
uncommit.py Loading ...
win32mbcs.py Loading ...
win32text.py Loading ...