mention git-annex export
This commit is contained in:
parent
165725b9df
commit
34ad1c15e8
4 changed files with 35 additions and 1 deletions
|
@ -17,4 +17,7 @@ Thank you!
|
|||
|
||||
> I don't think this is something git-annex can usefully do.
|
||||
> Instead, see
|
||||
> <http://git-annex.branchable.com/tips/public_Amazon_S3_remote/>. [[done]] --[[Joey]]
|
||||
> <http://git-annex.branchable.com/tips/public_Amazon_S3_remote/>. --[[Joey]]
|
||||
|
||||
> [[done]]; the new `git-annex export` feature allows you to export a tree
|
||||
> to a special remote. --[[Joey]]
|
||||
|
|
|
@ -10,3 +10,6 @@ I know this would have several downsides:
|
|||
* much more exposed to corruption (no checksum to check against recorded? or can this be put somewhere else?)
|
||||
|
||||
The main advantage, for me, is much better interoperability: any remote becomes usable by other non-git-annex clients... It would also be great as it would allow me to store only a *part* of my git-annex files on a remote without having a forest of empty files (on broken filesystems) or symlinks (on real filesystems) for files that are missing, something that is a massive source of confusion for users I work with. It could, for example, allow me to create thumb drives that would solve the [[hide missing files]] problem. -- [[anarcat]]
|
||||
|
||||
> [[done]]; the new `git-annex export` feature allows you to export a tree
|
||||
> to a special remote. --[[Joey]]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue