From: Jeff King <peff@peff.net>
To: kusmabite@gmail.com
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: strange error while pushing
Date: Sun, 13 Dec 2009 18:02:14 -0500 [thread overview]
Message-ID: <20091213230214.GA27365@sigill.intra.peff.net> (raw)
In-Reply-To: <40aa078e0912131441i370d9c23r65c42fe1f46bd194@mail.gmail.com>
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
next prev parent reply other threads:[~2009-12-13 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 22:41 strange error while pushing Erik Faye-Lund
2009-12-13 22:57 ` Erik Faye-Lund
2009-12-13 23:02 ` Jeff King [this message]
2009-12-13 23:08 ` Erik Faye-Lund
2009-12-14 0:01 ` Sverre Rabbelier
2009-12-14 11:35 ` Johannes Schindelin
2009-12-14 11:33 ` Sverre Rabbelier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091213230214.GA27365@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox