mirror of
https://github.com/martinvonz/jj.git
synced 2024-09-11 05:45:30 +03:00
readme: clarify that snapshotting doesn't result in a chain of commits
It's not clear at all right now that snapshotting the working copy results in it being amended.
This commit is contained in:
parent
82be7f727c
commit
b6c65c12ac
17
README.md
17
README.md
@ -63,13 +63,16 @@ add functionality that cannot easily be added to the Git backend.
|
|||||||
|
|
||||||
### The working copy is automatically committed
|
### The working copy is automatically committed
|
||||||
|
|
||||||
Almost all Jujutsu commands automatically commit the working copy. That means
|
Jujutsu uses a real commit to represent the working copy. Checking out a commit
|
||||||
that commands never fail because the working copy is dirty (no "error: Your
|
results a new working-copy commit on top of the target commit. Almost all
|
||||||
local changes to the following files..."), and there is no need for `git stash`.
|
commands automatically amend the working-copy commit.
|
||||||
You also get an automatic backup of the working copy whenever you run a command.
|
|
||||||
Also, because the working copy is a commit, commands work the same way on the
|
The working-copy being a commit means that commands never fail because the
|
||||||
working-copy commit as on any other commit, so you can set the commit message
|
working copy is dirty (no "error: Your local changes to the following
|
||||||
before you're done with the changes.
|
files..."), and there is no need for `git stash`. Also, because the working copy
|
||||||
|
is a commit, commands work the same way on the working-copy commit as on any
|
||||||
|
other commit, so you can set the commit message before you're done with the
|
||||||
|
changes.
|
||||||
|
|
||||||
<img src="demos/working_copy.png" />
|
<img src="demos/working_copy.png" />
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user