diff options
author | wsha.code+ga@b38779424f41c5701bbe5937340be43ff1474b2d <wshacodega@web> | 2016-01-16 13:03:26 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2016-01-16 13:03:26 +0000 |
commit | 8978c18062e01e44e330cf82d52e0b0c83a42086 (patch) | |
tree | df3a500838ce904f60d1bc8b11c6457c62946430 | |
parent | 656bb6c8b4efeca5f331738149eb01889bcf36b6 (diff) |
Added a comment
-rw-r--r-- | doc/tips/unlocked_files/comment_3_f5f29661bd04a6bba6158307465981d9._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/tips/unlocked_files/comment_3_f5f29661bd04a6bba6158307465981d9._comment b/doc/tips/unlocked_files/comment_3_f5f29661bd04a6bba6158307465981d9._comment new file mode 100644 index 000000000..435afcdcf --- /dev/null +++ b/doc/tips/unlocked_files/comment_3_f5f29661bd04a6bba6158307465981d9._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="wsha.code+ga@b38779424f41c5701bbe5937340be43ff1474b2d" + nickname="wsha.code+ga" + subject="comment 3" + date="2016-01-16T13:03:26Z" + content=""" +1. If you want to save a committed version of a file, is there a way to do that, other than `sync`ing to a remote that does not have `annex.thin` set? +2. If you `add` and `commit` a file multiple times in a repo without `sync`ing to a remote, what does the commit history look like on a remote when you do `sync` it? It just has several commits for which the file contents are not available? +3. If you want to preserve history with `annex.thin` set, do you just have to `sync` manually after each commit? I guess you might want to set up a git commit hook to do that in that case. +"""]] |