From 47e7921259a365970ccec1c8dc48fb8199d78f91 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 11 Aug 2015 13:21:47 -0400 Subject: [PATCH] response --- ..._a31a501bdc28eabc60588502f7219e50._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/forum/checkout_view_to_directory_outside_of_annex/comment_1_a31a501bdc28eabc60588502f7219e50._comment diff --git a/doc/forum/checkout_view_to_directory_outside_of_annex/comment_1_a31a501bdc28eabc60588502f7219e50._comment b/doc/forum/checkout_view_to_directory_outside_of_annex/comment_1_a31a501bdc28eabc60588502f7219e50._comment new file mode 100644 index 0000000000..a0d1f4dab7 --- /dev/null +++ b/doc/forum/checkout_view_to_directory_outside_of_annex/comment_1_a31a501bdc28eabc60588502f7219e50._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-08-11T16:57:45Z" + content=""" +Well, you can certianly use --work-tree with git-annex. As a global git +option, it has to be passed after the "git" and before the "annex". However, +since the view is constructed by making symlinks to the annexed content, +the result will be a directory full of symlinks, rather than the contents +of the files. Also, it'll still update the repo to think it has this view +checked out, with confusing results. + +rsync seems to be a perfectly good way to do what you want, if you want +to have copies of the files. + +Or, you might consider making a shared clone of the git repo wherever you +want that tree of files, and checking out the desired view in the clone. +In a shared clone with a recent version of git-annex, running `git annex +get` will quickly hard-link the files from the main repo (when possible). +"""]]