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

mention git-annex export

Browse source
This commit is contained in:
Joey Hess 2017-09-07 16:17:46 -04:00
parent 165725b9df
commit 34ad1c15e8
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 35 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
doc/todo/Facilitate_public_pretty_S3_URLs.mdwn
View file

@ -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]]

3
doc/todo/dumb__44___unsafe__44___human-readable_backend.mdwn
View file

@ -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]]