Added a comment
This commit is contained in:
parent
a368e33f4a
commit
528e3323c5
1 changed files with 14 additions and 0 deletions
|
@ -0,0 +1,14 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://id.koumbit.net/anarcat"
|
||||
subject="comment 1"
|
||||
date="2015-02-15T05:46:01Z"
|
||||
content="""
|
||||
> This way, if a file has a staged change, it gets committed, and then that commit is reverted, resulting in another commit. Which a later run of undo can in turn revert. If it didn't commit, the history about the staged change that was reverted would be lost.
|
||||
|
||||
so far, my experience with this is that unstaged changes get dropped and the change that gets undoed is the last committed change. In other words, if i have:
|
||||
|
||||
$ git annex status
|
||||
M file
|
||||
|
||||
`git annex undo` is going to drop that modification and `git revert HEAD`. but maybe i got confused, in which care some of the documentation i just did in [[direct mode]] needs to be corrected. --[[anarcat]]
|
||||
"""]]
|
Loading…
Add table
Reference in a new issue