Re: Confusing commit messages about `type-nats`?

On Tue, Feb 26, 2013 at 11:25:17PM +0100, Gabor Greif wrote:

On 2/26/13, Iavor Diatchki wrote:

...

I am receiving a bunch of commit messages for branch `type-nats`, that seem to be fake (i.e., by folks committing to other branches). Does any one know why that is? It seems to have started after my merge commit from yesterday, so did I mess something up?

I guess it is a 'git' bug (or something from the connected ecosystem). I commented on ghc-commits this morning. Maybe the mailer is stuck on the type-nats branch?

It's to do with this failure: igloo@abbot:/srv/darcs/ghc.git$ git show -v 41c44e4db3105d8f4bc78ffcd4fc30764ab788d8 > /dev/null; echo $? fatal: object 'e168baae424a6d4e8b138021b90743b5e7728a80' is not a blob! 128 e168baae424a6d4e8b138021b90743b5e7728a80 is a change in a submodule (Cabal), and abbot has an old git version which apparently doesn't handle it properly. Unfortunately, abbot is still on lenny, which doesn't have a newer version of git packaged. Maybe I should just build it by hand. For now I've disabled the notification script so that we don't get the broken mails. Thanks Ian