From: Michael Haggerty <mhagger@alum.mit.edu>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: Junio C Hamano <gitster@pobox.com>,
git discussion list <git@vger.kernel.org>
Subject: Re: Breakage in master since 6d4bb3833c
Date: Fri, 21 Oct 2011 16:01:01 +0200 [thread overview]
Message-ID: <4EA17B1D.9000900@alum.mit.edu> (raw)
In-Reply-To: <20111021122801.GA3799@goldbirke>
On 10/21/2011 02:28 PM, SZEDER Gábor wrote:
> On Fri, Oct 21, 2011 at 02:10:53PM +0200, Michael Haggerty wrote:
>> When testing reference-handling performance using my refperf script [1],
>> I noticed that there is a problem in master that I bisected down to
>>
>> 6d4bb3833c "fetch: verify we have everything we need before updating our
>> ref"
>>
>> When I run the following commands
>>
>> =======================================================
>> GIT=$(pwd)/git
>
>> $GIT fetch origin
>> Then the last "git fetch origin" command gives the following output:
>> remote: Counting objects: 3, done.
>> remote: Total 3 (delta 0), reused 0 (delta 0)
>> Unpacking objects: 100% (3/3), done.
>> usage: git rev-list [OPTION] <commit-id>... [ -- paths... ]
>
> I suspect this is the same issue as here:
>
> http://thread.gmane.org/gmane.comp.version-control.git/182339/focus=182357
Yes, you are right. Setting GIT=$(pwd)/bin-wrappers/git fixes the problem.
Thanks,
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2011-10-21 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 12:10 Breakage in master since 6d4bb3833c Michael Haggerty
2011-10-21 12:28 ` SZEDER Gábor
2011-10-21 14:01 ` Michael Haggerty [this message]
2011-10-21 17:01 ` Junio C Hamano
2011-10-22 5:11 ` Michael Haggerty
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=4EA17B1D.9000900@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder@ira.uka.de \
/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;
as well as URLs for NNTP newsgroup(s).