> NOTE: Task failed: Fetch failed: Fetch command export
> git fetch git://git.openmoko.org/git/kernel.git stable failed with signal
> 128, output:
> fatal: The remote end hung up unexpectedly
> fatal: Fetch failure: git://git.openmoko.org/git/kernel.git
The git.openmoko.org server seems to be acting up. Since I set up a
mirror of it on repo.or.cz, I receive a message whenever repo fails to
mirror (and whenever it starts working again). I already received two
failures today (both already recovered), both of the same type:
git mirror git://git.openmoko.org/git/kernel.git failed with error code 0
you will not receive any more notifications until recovery
fatal: The remote end hung up unexpectedly
ls-remote git://git.openmoko.org/git/kernel.git: command returned error: 128
Just keep trying until the server comes back (or, if you know how to do
it, temporarily point the recipe to the mirror at repo.or.cz, which
shouuld be more stable but about an hour behind git.openmoko.org).
I would recommend "git gc" instead, which not only does a "git repack -a
-d -l", but also cleans up some other stuff.
Another option would be running "git gc --auto" often; it does nothing
until there are over 6700 loose objects, which it then packs on a new
pack, and it condenses all packs into one (like "git repack -a -d -l")
when there are over 50 packs (both values are configurable). Since it's
much more lightweight (except when it decides to do a full repack), it
can be run very often (and in fact some commands run it automatically).
And, as a comment in the blog post said, using "git count-objects" is
better than "find objects | cut -d/ -f3 | wc -w" (but if you are using
that, "git gc --auto" is usually better).