Pushing a git note fails.

[Mike Frysinger]

On Saturday 06 April 2013 19:08:48 Carlos O'Donell wrote:
> On 04/06/2013 06:22 PM, Andreas Schwab wrote:
> > "Carlos O'Donell" <carlos@redhat.com> writes:
> >> For the default 'commit' namespace notes we don't want
> >> any restrictions. That makes the commit notes perfectly
> >> usable for writing whatever you want to say in a followup
> >> to the original commit message.
> > 
> > I think you still want it fast-forward only.
> 
> Why?

like a normal tree, you don't want people to clobber existing work.  i think 
you'd get an error currently though and you'd have to force it to go through 
by using --force.

i'm guessing if you edit a note on an existing commit, there's no way to 
"merge" that change, so a non-fast-forward update is the only option.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20130407/3ff2ab85/attachment.sig>