comment
authorJoey Hess <joeyh@joeyh.name>
Wed, 2 Dec 2015 18:19:31 +0000 (14:19 -0400)
committerJoey Hess <joeyh@joeyh.name>
Wed, 2 Dec 2015 18:19:31 +0000 (14:19 -0400)
doc/forum/Does_git_annex_support_my_weird_workflow__63_____40__A_single__44___effectively___95__read_only__95___source__41__/comment_1_25572571debe2c91447b0ed952f45cb2._comment [new file with mode: 0644]

diff --git a/doc/forum/Does_git_annex_support_my_weird_workflow__63_____40__A_single__44___effectively___95__read_only__95___source__41__/comment_1_25572571debe2c91447b0ed952f45cb2._comment b/doc/forum/Does_git_annex_support_my_weird_workflow__63_____40__A_single__44___effectively___95__read_only__95___source__41__/comment_1_25572571debe2c91447b0ed952f45cb2._comment
new file mode 100644 (file)
index 0000000..eb56864
--- /dev/null
@@ -0,0 +1,19 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-12-02T18:14:50Z"
+ content="""
+The two problems are: Read-only directory, and wanting a clone that doesn't
+have the same directory structure.
+
+For the read-only directory, you may be able to use a direct mode
+repository. You might need to set `GIT_DIR` in the environment to make
+the .git directory be placed somewhere outside the read-only directory.
+
+As to wanting different directory structure in your clone, it's an added
+complication I'd recommend avoiding. Not that it's impossible, you can move
+files around in the git repository and that could be automated via
+git-filter-branch or the like. But git-annex offers a simpler solution,
+which is to use the same directory structure and only get the contents of
+files in the subdirectories you want.
+"""]]