responses
This commit is contained in:
parent
24883e01cd
commit
81926f638e
2 changed files with 28 additions and 0 deletions
|
@ -0,0 +1,9 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 6"""
|
||||||
|
date="2017-10-30T16:04:24Z"
|
||||||
|
content="""
|
||||||
|
You should be able to run `git annex export` in the bare git repository on
|
||||||
|
your server. It just needs the branch you want to export to be known to
|
||||||
|
git, and the annexed file contents to be available there.
|
||||||
|
"""]]
|
|
@ -0,0 +1,19 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""Re: Publishing subdir is publishing files but not subdir?"""
|
||||||
|
date="2017-10-30T16:06:36Z"
|
||||||
|
content="""
|
||||||
|
The reason exporting a subdir puts the files at the root of the folder
|
||||||
|
is that it's exporting a git tree, and files in the tree of a subdir
|
||||||
|
are relative to that subdir.
|
||||||
|
|
||||||
|
It's certianly possible to make git construct a tree object that
|
||||||
|
contains a subdirectory containing the files you want to export, and
|
||||||
|
then exporting that tree object would replicate that tree structure,
|
||||||
|
including the subdir. One way is to check out a branch, delete the files
|
||||||
|
you don't want to export and once things are arranged as you like,
|
||||||
|
commit to that branch and then export it.
|
||||||
|
|
||||||
|
(Or you could just make the webdav special remote's url include the
|
||||||
|
subdir where you wanrt it to export stuff.)
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue