From 44973c570c91915d82970a42d9a9d9d2f91bc3e1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 4 Feb 2015 15:47:29 -0400 Subject: comment --- ...ent_1_08f8f27e5a8dbd80a91ffd9fd6f64e6c._comment | 23 ++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/bugs/Configuring_metadata_view_filenames/comment_1_08f8f27e5a8dbd80a91ffd9fd6f64e6c._comment (limited to 'doc') diff --git a/doc/bugs/Configuring_metadata_view_filenames/comment_1_08f8f27e5a8dbd80a91ffd9fd6f64e6c._comment b/doc/bugs/Configuring_metadata_view_filenames/comment_1_08f8f27e5a8dbd80a91ffd9fd6f64e6c._comment new file mode 100644 index 000000000..b498df631 --- /dev/null +++ b/doc/bugs/Configuring_metadata_view_filenames/comment_1_08f8f27e5a8dbd80a91ffd9fd6f64e6c._comment @@ -0,0 +1,23 @@ +[[!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. +"""]] -- cgit v1.2.3