{"thread":{"id":"26397","subject":"Re: [1.8.0] Tracking empty directories","startedAt":"2011-02-03T11:07:53Z","lastAt":"2011-02-03T11:07:53Z","messageCount":1,"participants":["Yann Dirson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"160322","messageId":"20110203120753.6636d0cd@chalon.bertin.fr","threadId":"26397","inReplyTo":null,"subject":"Re: [1.8.0] Tracking empty directories","fromName":"Yann Dirson","fromEmail":"dirson@bertin.fr","sentAt":"2011-02-03T11:07:53Z","receivedAt":"2011-02-03T11:07:53Z","isPatch":false,"sender":{"key":"dirson@bertin.fr","avatar":null},"body":"Jonathan wrote:\n>What might make git nice as an interoperability tool is that it tracks\n>the _relevant_ information for the history of a software project.\n>Example of what is not relevant information and why that matters:\n>\n> http://thread.gmane.org/gmane.comp.version-control.git/53494\n\nHell, that message seems to even suggest a potential solution:\nuse .gitattributes for tracking empty dirs.  That way a post-change\n\"git checkout-index\" could find the info (from .gitattribute in the index)\nwithout confusing any pre-change tool.\n\nFor ease of use, some porcelain could possibly be taught to add empty\ndirectories into $GIT_DIR/.gitattribute (as well as checking whether an\nempty-dir entry has turned useless because it now has content, and any\nother administrative stuff we could want).\n\n\nBut that idea is linked to another issue, which could be the subject\nof a 1.8 proposal of its own: the handling of .gitattribute, for which\nonly the checked-out version is taken into account:\n\nhttp://marc.info/?l=git&m=126458888515166\n\n-- \nYann Dirson - Bertin Technologies\n"}]}