From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>,
git discussion list <git@vger.kernel.org>
Subject: Breakage in master since 6d4bb3833c
Date: Fri, 21 Oct 2011 14:10:53 +0200 [thread overview]
Message-ID: <4EA1614D.3090202@alum.mit.edu> (raw)
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
ORIG=bug-6d4bb383-repo
REPO=bug-6d4bb383-clone
URL=file://$(pwd)/$ORIG
$GIT init $ORIG
cd $ORIG
$GIT config gc.auto 0
$GIT config gc.packrefs false
touch a.txt
$GIT add a.txt
$GIT commit -am 'Add file'
cd ..
mkdir $REPO
cd $REPO
$GIT init
$GIT remote add origin $URL
$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... ]
limiting output:
--max-count=<n>
--max-age=<epoch>
--min-age=<epoch>
--sparse
--no-merges
--min-parents=<n>
--no-min-parents
--max-parents=<n>
--no-max-parents
--remove-empty
--all
--branches
--tags
--remotes
--stdin
--quiet
ordering output:
--topo-order
--date-order
--reverse
formatting output:
--parents
--children
--objects | --objects-edge
--unpacked
--header | --pretty
--abbrev=<n> | --no-abbrev
--abbrev-commit
--left-right
special purpose:
--bisect
--bisect-vars
--bisect-all
error: file:///home/mhagger/self/proj/git/git/bug-6d4bb383-repo did not
send all necessary objects
=======================================================
The same error occurs if all of the steps *except* the last one are done
with a release version of git.
Michael
[1] branch "refperf" at git://github.com/mhagger/git.git
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next reply other threads:[~2011-10-21 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 12:10 Michael Haggerty [this message]
2011-10-21 12:28 ` Breakage in master since 6d4bb3833c SZEDER Gábor
2011-10-21 14:01 ` Michael Haggerty
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=4EA1614D.3090202@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.