{"thread":{"id":"39076","subject":"Error staging submodule removal when empty directory present","startedAt":"2015-04-14T18:23:27Z","lastAt":"2015-04-14T18:23:27Z","messageCount":1,"participants":["Josh Hagins"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"259366","messageId":"CANuW5x3N07ftrYmTF8LihHNEUsA=nn=b_EcOQ7BPYjOMfkDtVA@mail.gmail.com","threadId":"39076","inReplyTo":null,"subject":"Error staging submodule removal when empty directory present","fromName":"Josh Hagins","fromEmail":"hagins.josh@gmail.com","sentAt":"2015-04-14T18:23:27Z","receivedAt":"2015-04-14T18:23:27Z","isPatch":false,"sender":{"key":"hagins.josh@gmail.com","avatar":null},"body":"I'm having a hard time understanding why ``git stash save\" chokes on a\nsubmodule removal when an empty directory is present at the removed\nsubmodule's path. If the submodule is staged for deletion, why not\njust leave the empty directory alone?\n\nThe following Gist illustrates the situation I am encountering, and\nincludes OS information, Git version (2.3.5), and GIT_TRACE output:\nhttps://gist.github.com/jawshooah/d60ff70952cff18099d7\n\nRelevant post in the git-users Google Group, where I was encouraged to\nquery the mailing list:\nhttps://groups.google.com/forum/#!topic/git-users/3YxxpVVXtqg\n\nThanks,\nJosh\n"}]}