"Shawn O. Pearce" <spearce@xxxxxxxxxxx> wrote:
> Junio C Hamano <gitster@xxxxxxxxx> wrote:
> > * db/fetch-pack (Fri Sep 14 03:31:25 2007 -0400) 22 commits
> ...
> > This is Daniel's fetch-pack in C plus fixups from Shawn.
> > Unfortunately the fixups breaks t3200 ("*** glibc detected ***
> > fetch: free(): invalid pointer xxx ***"), which I haven't looked
> > into yet.
>
> Doesn't crash out on my Mac OS X system but I am getting the
> above failure on my amd64 Linux system.
OK, so in addition to the above fixups Junio mentions I have
also sent two more series today:
2 patch "fixup of the fixup" to resolve the t3200 crash
5 patch "fixup + cleanup" of http support
and now I just discovered that pushing to yourself is probably also
broken by this series:
$ git push . jc/maint:gfi-maint
updating 'refs/heads/gfi-maint' using 'refs/remotes/jc/maint'
from 05cc2ffc572f05e8aeec495a9ab9bc9609863491
to 8419d2ee9ba8b375186a5c1019df8dfbce610aba
Also local refs/heads/gfi-maint
Generating pack...
Done counting 0 objects.
Writing 0 objects...
Unpacking 0 objects...
error: Ref refs/heads/gfi-maint is at 8419d2ee9ba8b375186a5c1019df8dfbce610aba but expected 05cc2ffc572f05e8aeec495a9ab9bc9609863491
error: failed to lock refs/heads/gfi-maint
Total 0 (delta 0), reused 0 (delta 0)
ng refs/heads/gfi-maint failed to lock
error: failed to push to '.'
What's really exciting is we actually updated the ref 'gfi-maint',
even though it was "ng" and we failed to push. Yup. More work
for me to look at tomorrow. Right now I think I'm all memory
corruptioned out for *** brain detected *** Shawn(): nextword():
too tired, try sleep ***
;-)
--
Shawn.
-
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
