From 592f3903b3b0e0b1a433f0a4abfea270ce93c605 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Thu, 2 Oct 2014 15:40:40 +0000 Subject: Added a comment --- .../comment_3_15f36487383a631f16e041e2885c44ec._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Direct_Mode_-_Restore_file_from_Full_Backup_Repository__63__/comment_3_15f36487383a631f16e041e2885c44ec._comment diff --git a/doc/forum/Direct_Mode_-_Restore_file_from_Full_Backup_Repository__63__/comment_3_15f36487383a631f16e041e2885c44ec._comment b/doc/forum/Direct_Mode_-_Restore_file_from_Full_Backup_Repository__63__/comment_3_15f36487383a631f16e041e2885c44ec._comment new file mode 100644 index 000000000..99dd7e81b --- /dev/null +++ b/doc/forum/Direct_Mode_-_Restore_file_from_Full_Backup_Repository__63__/comment_3_15f36487383a631f16e041e2885c44ec._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.54" + subject="comment 3" + date="2014-10-02T15:40:40Z" + content=""" +Using git does not affect the timestamps or other metadata of files stored by git-annex, which git knows nothing about. It will perhaps change the timestamps of the symlinks that git changes. It you really wanted to avoid that, you could `git clone` the repository and do all the git commands in the clone of the repository, without touching the original repo. + +Whether commands like `git checkout` and `git revert` are intuitive depends on how intuitive you find git, I suppose. It sure seems more intuitive to me to reuse git commands that work just fine, rather than adding a whole new set of commands. +"""]] -- cgit v1.2.3