mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2017-07-12 12:56:13 -04:00
parent ecad2da8c5
commit 5342c5064b
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 24 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
doc/design/exporting_trees_to_special_remotes/comment_4_126ee5332ff88b3993d33d59328d4148._comment Normal file
View file

@ -0,0 +1,24 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2017-07-12T16:45:51Z"
content="""
I've added a section with changes to the external special remote protocol.
I included the Key in each of the new protocol commands, although it's not
strictly neeed, to allow the implementation to use SETURLPRESENT, SETSTATE,
etc.
`git annex copy $file --to myexport` could perhaps work; the difficulty
though is, what if you've exported branch foo, and then checked out bar,
and so you told it to export one version of the file, and are running
git-annex copy on a different version? It seems that git-annex would have
to cross-check in this and similar commands, to detect such a situation.
Unsure how much more work that would be, both CPU time and implementation
time.
I do think that `git annex get` could download files from exports easily
enough, but see the "location tracking" section for trust caveats.
I'm not clear about what you're suggesting be done with versioning support
in external special remotest?
"""]]