diff options
| author |  mitzip <mitzip@web> | 2015-05-27 22:43:03 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-05-27 22:43:03 +0000 |
| commit | 8d1fa8a05ff965d6bf3a29eb4dd66b1a4d7d3cc9 (patch) | |
| tree | 936b851b7c4d77245c52221368365b533aaf6b40 | |
| parent | 15a21216fb21598e46a845249e9e2fefc12c4db6 (diff) | |
| -rw-r--r-- | doc/forum/Proper_usage_of_git_annex_proxy_to_mimc_undo_--depth.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/forum/Proper_usage_of_git_annex_proxy_to_mimc_undo_--depth.mdwn b/doc/forum/Proper_usage_of_git_annex_proxy_to_mimc_undo_--depth.mdwn index 6a02fed78..1f15d6655 100644 --- a/doc/forum/Proper_usage_of_git_annex_proxy_to_mimc_undo_--depth.mdwn +++ b/doc/forum/Proper_usage_of_git_annex_proxy_to_mimc_undo_--depth.mdwn @@ -12,4 +12,4 @@ So annex, thorough as it is, creates a `$filename.variant-local.$ext` file after The issue it seems is that `git revert` works on a commit basis, while `git checkout` can operate on files. If I'm correct in this it would be good to know if annex uses one commit per file, for sure, every time? If this is the case, there would be no problem using the better in most every other way `git revert`. -Though, I'm still not clear how to use the "depth" referencing with git revert rather than hashes, any suggestions? +Though, I'm still not clear how to use the "depth" referencing with `git revert` rather than hashes, any suggestions? |