From 1cfbc91375c4f10d0fdd7ca025afc19eb25be4d9 Mon Sep 17 00:00:00 2001 From: gan Date: Sat, 7 Dec 2013 01:15:47 +0000 Subject: [PATCH 1/2] Added a comment: Hook implementation? --- ...omment_8_21712dfee4f37232c34eddbce2427691._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/todo/New_special_remote_suggeston_-_clean_directory/comment_8_21712dfee4f37232c34eddbce2427691._comment diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_8_21712dfee4f37232c34eddbce2427691._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_8_21712dfee4f37232c34eddbce2427691._comment new file mode 100644 index 0000000000..3aeb04e53e --- /dev/null +++ b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_8_21712dfee4f37232c34eddbce2427691._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="gan" + ip="85.224.8.104" + subject="Hook implementation?" + date="2013-12-07T01:15:46Z" + content=""" +1. I would propose the name \"plain directory\" for this special remote. Clean is not a good description, IMHO. + +2. When I read this a week ago I took the opportunity to play with the special remote hook, because as far as I can understand this could be a relatively trivial implementation that need not necessarily be in git-annex \"core\". And I'd like to contribute back to the git-annex community and help a brother out... I used the method of calling a single script from all hook points, and inside it look at what operation was requested. +I didn't get that far before giving up however. I got the feeling that hook would benefit from some extension and a bit more complete API to really create the opportunity for third-party extensions to git-annex this way. I would prefer that the hook script can handle several instances of remotes without creating custom hook scripts for each instance. Specifically I think a hook is needed also for \"init\" of a new remote (to get a unique identifier, and other parameters given by the user such as in this particular case, the path to the \"clean directory\") What do you think? +"""]] From c3d1572e1f0ceac38615254c58b50756a984b6ac Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlnhME0DDX-SviTAJ_NOH8nZmfgli3z6YQ" Date: Sat, 7 Dec 2013 08:19:49 +0000 Subject: [PATCH 2/2] --- doc/forum/handling_MP3_metadata_changes.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/handling_MP3_metadata_changes.txt diff --git a/doc/forum/handling_MP3_metadata_changes.txt b/doc/forum/handling_MP3_metadata_changes.txt new file mode 100644 index 0000000000..9b6caa27aa --- /dev/null +++ b/doc/forum/handling_MP3_metadata_changes.txt @@ -0,0 +1,12 @@ +Hello, + +I'm still looking for a way to version control the metadata (title, artist, album name, ...) of my MP3s, I wonder if git annex could help for this problem ? +The method I use now (without git annex) is to export the MP3 metadata to an textual format with one line per tag. +It's this textual file I handles with git. +The problem is to handle the mapping between the orignal file and the export file with file renaming or moving. +I consider to use the checksum of the audio content (without metadata, this checksum never changes) to handle this problem. +Maybe git annex has a different approach (better) to solve this problem ? +How git annex would be use to solve the orignal problem ? + +Regards, +Emmanuel Berry