On Fri, Sep 16, 2016 at 12:48 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Aviv Eyal <avivey@xxxxxxxxx> writes: > >> Using `git add -N` allows creating of empty commits: >> >> git init test && cd test >> echo text > file >> git add --intent-to-add file >> git commit -m 'Empty commit' >> echo $? # prints 0 >> ... >> I'd expect `git commit` to error out instead of producing an empty commit. >> >> I've seen this with git 2.8.1 and 2.10.0.129.g35f6318 > > I think I've seen this reported some time ago. > > https://public-inbox.org/git/%3CCACsJy8A8-RgpYxYsJBaLrMia7D3DfQPr4cxASNsaLyCnmgm3ZQ@xxxxxxxxxxxxxx%3E/ > > I do not offhand recall what happend to the topic after that. Yeah. I'm a bit behind, no, I'm waaaay behind my git backlog. This definitely gets a rise-up, together with the multiworktree bug fix in git-init. -- Duy