This commit is contained in:
parent
60612a3192
commit
25e7243cbd
1 changed files with 19 additions and 0 deletions
19
doc/todo/whishlist:_temporary_relinking_to_remotes.mdwn
Normal file
19
doc/todo/whishlist:_temporary_relinking_to_remotes.mdwn
Normal file
|
@ -0,0 +1,19 @@
|
|||
Imagine the following situation:
|
||||
You have a directory structure like this:
|
||||
|
||||
`./`
|
||||
`+--dir1`
|
||||
`|+--file1 (local)`
|
||||
`|+--file2 (remote1)`
|
||||
`|+--file3 (remote2)`
|
||||
|
||||
Now when these files are quite big and you need them in one directory temporarily you would need to use `git annex get dir1` to copy them all over to local. This can take some time.
|
||||
|
||||
I whish we had a command like this:
|
||||
`git annex getlinks dir1`
|
||||
where git annex would try to not link to the missing local objects but to the remote ones. So there is no need to copy the data around just to use it for a short time. After you are done you could use `git annex resetlinks dir1` to reset the links to the local objects.
|
||||
|
||||
I know that many specialremotes will not support this without much hassle, but it would be cool to be able to get atleast the links from external drives and maybe ssh remotes via sshfs.
|
||||
To keep the data consistent there can be a constraint that every action (add, sync, commit or others) first issue a `resetlinks`.
|
||||
|
||||
What do you think of that?
|
Loading…
Add table
Add a link
Reference in a new issue