On Sun, Dec 13, 2009 at 11:41:49PM +0100, Erik Faye-Lund wrote:
> I was going to push some stuff I'm working on to my repo at
> repo.or.cz, and just got the following error:
>
> $ GIT_TRACE=1 git push kusma work/daemon-win32:work/daemon-win32-process
> trace: built-in: git 'push' 'kusma'
> 'work/daemon-win32:work/daemon-win32-process'
> trace: run_command: 'ssh' 'repo.or.cz' 'git-receive-pack
> '\''/srv/git/git/kusma.git'\'''
> trace: run_command: 'pack-objects' '--all-progress-implied' '--revs'
> '--stdout' '--thin'
> trace: built-in: git 'pack-objects' '--all-progress-implied' '--revs'
> '--stdout' '--thin'
I notice your pack-objects is being called with the new
--all-progress-implied, and then you get a usage error with
pack-objects:
> 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?
-Peff
--
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