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

update

Browse source
This commit is contained in:
Joey Hess 2014-02-24 14:45:19 -04:00
parent 8d5158fa31
commit 0506764fc3
1 changed files with 6 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

15
doc/design/metadata.mdwn
View file

@ -172,14 +172,15 @@ So, possible approaches:
* Git has a complex set of rules for what is legal in a ref name. * Git has a complex set of rules for what is legal in a ref name.
View branch names will need to filter out any illegal stuff. **done** View branch names will need to filter out any illegal stuff. **done**
* Metadata should be copied to the new key when adding a modified version
of a file. **done**
* Filesystems that are not case sensative (including case preserving OSX) * Filesystems that are not case sensative (including case preserving OSX)
will cause problems if view branches try to use different cases for will cause problems if view branches try to use different cases for
2 directories representing the value of some metadata. But, users 2 directories representing a metadata field.
probably want at least case-preserving metadata values.
Solution might be to compare metadata case-insensitively, and Solution might be to compare fields names case-insensitively, and
pick one representation consistently, so if, for example an author pick one representation consistently.
field uses mixed case, it will be used in the view branch.
Alternatively, it could escape `A` to `_A` when such a filesystem Alternatively, it could escape `A` to `_A` when such a filesystem
is detected and avoid collisions that way (double `_` to escape it). is detected and avoid collisions that way (double `_` to escape it).
@ -198,7 +199,3 @@ So, possible approaches:
* The filename mangling can result in a filename in a view * The filename mangling can result in a filename in a view
that is too long for its containing filesystem. Should detect and do that is too long for its containing filesystem. Should detect and do
something reasonable to avoid. TODO something reasonable to avoid. TODO
* When a file is edited and the new version committed, the new key
does not inherit the metadata of the old key. Which may be right
sometimes, but more generally violates least surprise.