{"thread":{"id":"40121","subject":"list empty dirs in commit message trailer","startedAt":"2015-08-18T14:43:00Z","lastAt":"2015-08-18T14:43:00Z","messageCount":1,"participants":["Thomas Koch"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"268254","messageId":"2384709.cc1iR2nLxC@x121e","threadId":"40121","inReplyTo":null,"subject":"list empty dirs in commit message trailer","fromName":"Thomas Koch","fromEmail":"thomas@koch.ro","sentAt":"2015-08-18T14:43:00Z","receivedAt":"2015-08-18T14:43:00Z","isPatch":false,"sender":{"key":"thomas@koch.ro","avatar":null},"body":"Hi,\n\nI had an idea how to deal with tracking empty directories in git repositories \nwhen one does not want \".gitkeep\" files. Just add a trailer like:\n\nempty-dirs: a b/c a\\nnewline exploit\\\" &&\\ rm\\ -rf \\/ ..\n\nthis line would indicate that the worktree contained the empty directories a \nand b/c and contains examples for possible shell quoting problems or exploits.\n\nSo one can not just run mkdir -p and the content of the line but needs \nsafeguards.\n\nA pre-commit hook could add such a line to the commit message and another tool \ncould create the directories for HEAD. There is no staging in this approach \nfor empty directories and no ignore mechanism. But for my current use case \n(represent the content of debian source packages) this would be enough.\n\nDo you like the idea?\n\nRegards,\n\nThomas Koch\n"}]}