From c3d1572e1f0ceac38615254c58b50756a984b6ac Mon Sep 17 00:00:00 2001
From: 
 "https://www.google.com/accounts/o8/id?id=AItOawlnhME0DDX-SviTAJ_NOH8nZmfgli3z6YQ"
 <Emmanuel@web>
Date: Sat, 7 Dec 2013 08:19:49 +0000
Subject: [PATCH]

---
 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