On Tuesday 31 August 2010, Stefan Naewe wrote: > On 8/31/2010 11:07 AM, Johan Herland wrote: > > On Tuesday 31 August 2010, Stefan Naewe wrote: > >> And why does 'git remove' do that repetetively (is that even a > >> word...?), i.e. 'git add -m"Note" ; git remove; git remove; git > >> remove; git remove' creates 5 commit objects under > >> 'refs/notes/commits' Is that the intended behaviour ? > > > > Yes, this is the intended behaviour. Otherwise you would need a > > separate notes index where you could stage notes changes (with git > > notes add/remove), and then later commit those notes changes with > > (the imaginary) git notes commit. This was deemed too > > cumbersome/complicated, and we settled for the current approach > > instead. > > But if I do: > > $ touch file ; git add file ; git commit -m"add file" > > and then > > $ for n in 1 2 3; do git rm file; git commit -m"rm file"; done > > I get: > > rm 'file' > [master 5b24511] rm file > 0 files changed, 0 insertions(+), 0 deletions(-) > delete mode 100644 file > fatal: pathspec 'file' did not match any files > # On branch master > nothing to commit (working directory clean) > fatal: pathspec 'file' did not match any files > # On branch master > nothing to commit (working directory clean) > > I don't get 4 commits. That's the part I don't understand :-( > > Just to be clear: > > Of course I do understand why I don't get 4 commits here - I just > don't understand why I get a commit for every 'git notes remove' even > if there's nothing to remove. Ah, that would be a bug in 'git notes remove'. Patch coming soon. > And to delete the 'notes branch' I can only use 'git update-ref' ?! Yes, 'git update-ref -d refs/notes/foo' will delete the "foo" notes branch. ...Johan -- Johan Herland, <johan@xxxxxxxxxxx> www.herland.net -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html