{"thread":{"id":"3383","subject":"empty ident error on pull","startedAt":"2006-02-18T07:05:00Z","lastAt":"2006-02-18T07:05:00Z","messageCount":1,"participants":["carbonated beverage"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"16367","messageId":"20060218070500.GA12259@prophet.net-ronin.org","threadId":"3383","inReplyTo":null,"subject":"empty ident error on pull","fromName":"carbonated beverage","fromEmail":"ramune@net-ronin.org","sentAt":"2006-02-18T07:05:00Z","receivedAt":"2006-02-18T07:05:00Z","isPatch":false,"sender":{"key":"ramune@net-ronin.org","avatar":null},"body":"I'm tracking the Linux kernel repo via git, and got the following:\n\nbarbeque/zarathustra:linux-2.6: git pull\nUnpacking 885 objects\n 100% (885/885) done\n* refs/heads/origin: fast forward to branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6\nAuto-following refs/tags/v2.6.16-rc4\nUnpacking 1 objects\n 100% (1/1) done\n* refs/tags/v2.6.16-rc4: storing tag 'v2.6.16-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6\nTrying really trivial in-index merge...\nWonderful.\nfatal: empty ident  <barbeque@zarathustra.internal.psychosnugglebunnies.net.> not allowed\n\nThen I tried the following:\n\nbarbeque/zarathustra:linux-2.6: git-fsck-objects\ndangling tree 47678b69f7dcc6d5fcae007d1e4fe511fd260e5b\nbarbeque/zarathustra:linux-2.6: git prune\nbarbeque/zarathustra:linux-2.6: git-fsck-objects\nbarbeque/zarathustra:linux-2.6: git pull\n* refs/heads/origin: same as branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6\nTrying really trivial in-index merge...\nWonderful.\nfatal: empty ident  <barbeque@zarathustra.internal.psychosnugglebunnies.net.> not allowed\n\nOkay... so... what now?  I'm still a bit clueless when it comes to git.  Using\nit for some of my personal projects has gotten me a bit more comfortable with\nit, but my usage is still along the lines of \"CVS without warts\", for now.\n\n(And yes, it's the concept of the index file that's still throwing me for\na loop :-)\n\nI was tracking the repo with \"current\" versions of git until I got the above\nerror message the first time.  Went to a 1.1.6 tarball of git, pulled the\nrepro from scratch, all seemed well.  Upgraded to 1.2.1, tried a pull today,\nand got the above.\n\nThe system above is a Debian/sarge amd64 system, using gcc 3.3.5.\n\n-- DN\nDaniel\n"}]}