diff options
| author |  tom_clune <tom_clune@web> | 2016-02-24 22:19:00 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-02-24 22:19:00 +0000 |
| commit | 5970ccda425c8a32c513cf09d31f3708781639c8 (patch) | |
| tree | 919dbe75b1b07fa7c1caf4e277d6cf2c748afd99 | |
| parent | 2886280fac31edd07d6d6ecd68d342f44a7de6c1 (diff) | |
Added a comment: dropping files after changing branches/tags
| -rw-r--r-- | doc/walkthrough/unused_data/comment_4_2110ed6316b6a0df4ef3e1c8bc97ab99._comment | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/walkthrough/unused_data/comment_4_2110ed6316b6a0df4ef3e1c8bc97ab99._comment b/doc/walkthrough/unused_data/comment_4_2110ed6316b6a0df4ef3e1c8bc97ab99._comment new file mode 100644 index 000000000..8c6f04e27 --- /dev/null +++ b/doc/walkthrough/unused_data/comment_4_2110ed6316b6a0df4ef3e1c8bc97ab99._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="tom_clune" + subject="dropping files after changing branches/tags" + date="2016-02-24T22:19:00Z" + content=""" +I have a use case in which a colleague wishes to have a working copy of my data repository to use with the current version of my model. When a new version of the model is available they would likewise update their git-annex clone of my data. The colleague wants to drop any files that have been made obsolete by this change, but I do not see an efficient way to make this determination. They could of course drop everything and then do git annex get . but that could be very expensive if only a small subset of the files have actually changed. + +I'm probably just missing something basic, as this seems to be a reasonably frequent use case. + + +"""]] |