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

Browse source
This commit is contained in:
lukasz.opiola@8b366725db99c2a5e0e638d1a5d57d457d0bdad4 2024-04-08 13:56:32 +00:00 committed by admin
parent 58180abd6b
commit 5cb2186cd5
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
doc/todo/Idea_for_emulating_a_versioned_tree_export.mdwn
View file

@ -3,6 +3,7 @@ Dear Joey,
During DistriBits 2024, we discussed a concept that you seemed to like: emulating versioned tree export on a special remote with a non-versioned filesystem. This could be a generic mechanism of git-annex. Maybe a new option for the special remote (say: 'versioning = yes / no / emulated' or 'exporttree = yes / no / emulated')? During DistriBits 2024, we discussed a concept that you seemed to like: emulating versioned tree export on a special remote with a non-versioned filesystem. This could be a generic mechanism of git-annex. Maybe a new option for the special remote (say: 'versioning = yes / no / emulated' or 'exporttree = yes / no / emulated')?
The idea is to save target files in the remote at paths reflecting the ones in the repo, but: The idea is to save target files in the remote at paths reflecting the ones in the repo, but:
* create an extra directory at the end of the path identical to the filename, * create an extra directory at the end of the path identical to the filename,
* directory name includes the original extension of the file, which may seem a bit odd, but ensures no ambiguities, * directory name includes the original extension of the file, which may seem a bit odd, but ensures no ambiguities,
* inside the directory, save the file under filename = key (preferably add the original extension). * inside the directory, save the file under filename = key (preferably add the original extension).
@ -52,6 +53,7 @@ Example: the content of the git-annex repo and remote filesystem after a few tre
---------------------- ----------------------
Advantages: Advantages:
* easy to implement, * easy to implement,
* you get (kind of) versioning on any POSIX-like filesystem, * you get (kind of) versioning on any POSIX-like filesystem,
* older versions of files are never overwritten (history tracking), * older versions of files are never overwritten (history tracking),
@ -59,6 +61,7 @@ Advantages:
* users can use the remote filesystem directly, as it represents something meaningful. * users can use the remote filesystem directly, as it represents something meaningful.
Disadvantages: Disadvantages:
* not perfect, * not perfect,
* users need to accept the inconvenience caused by file naming on the bottom level, * users need to accept the inconvenience caused by file naming on the bottom level,
* it may be hard to find the right file version in the remote, especially if there are lots of them; * it may be hard to find the right file version in the remote, especially if there are lots of them;