On Mon, Dec 14, 2009 at 12:02 AM, Jeff King <peff@xxxxxxxx> wrote:
> On Sun, Dec 13, 2009 at 11:41:49PM +0100, Erik Faye-Lund wrote:
>> usage: git pack-objects [{ -q | --progress | --all-progress }]
>> [--max-pack-size=N] [--local] [--incremental]
>> [--window=N] [--window-memory=N] [--depth=N]
>> [--no-reuse-delta] [--no-reuse-object] [--delta-base-offset]
>> [--threads=N] [--non-empty] [--revs [--unpacked | --all]*] [--reflog]
>> [--stdout | base-name] [--include-tag]
>> [--keep-unreachable | --unpack-unreachable]
>> [<ref-list | <object-list]
>
> Is it possible you have a new git accidentally calling an old version of
> pack-objects?
>
Ah, yes it is! I just now tracked down the issue myself, and landed at
the same conclution. The reason? Simple, I was pushing git from a
directory with a recent git-binary, when my *installed* git was v1.6.4
;)
Running "make install" before pushing fixed the issue.
Thanks for wasting time on my PEBCAK :)
--
Erik "kusma" Faye-Lund
--
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