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

move to todo

Browse source
This commit is contained in:
Joey Hess 2015-02-04 15:47:36 -04:00
parent 130b58ca5b
commit 9a93de3d36
2 changed files with 0 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
doc/bugs/Configuring_metadata_view_filenames.mdwn
View file

@ -1 +0,0 @@
Currently, in a git annex view, filenames take the form basename%path%.ext. I understand that this is a carefully drafted mapping to allow changes to be merged back into metadata. However, maybe it would be possible to make the separator ('%') and the order (e.g. path%basename.ext instead) configurable?

23
doc/bugs/Configuring_metadata_view_filenames/comment_1_08f8f27e5a8dbd80a91ffd9fd6f64e6c._comment
View file

@ -1,23 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2015-02-04T19:38:58Z"
content="""
git-annex really doesn't care what filenames are used with in a view.
It only needs to ensure that each file gets a unique filename. Which
is why the directory is included in the filename, to avoid conflicts
if 2 files with the same name appear in different directories.
It would probably be better to make it avoid needing to include the
directory in the filename unless there is such a conflict, rather than
adding complexity configuring that.
However, since views are currently built by streaming the contents of the
branch to git update-index, git-annex can't just eg, examine the working
tree to see if a conflicting file exists. It seems it would need to keep
a map of the files it's added to the view branch so far, and check against
the map. But that would make memory use scale with the number of files in
the view, which I'd prefer to avoid..
I'm going to move this from bugs to todo.
"""]]