From: Rick Bradley <rick@rickbradley.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: problem with updating a shallow clone via a branch fetch
Date: Mon, 28 Feb 2011 20:07:35 -0600 [thread overview]
Message-ID: <AANLkTimSRG+UkD1vJszUf+3j0nV+_pPWSE3N2Dy9SfTa@mail.gmail.com> (raw)
In-Reply-To: <7vtyfng00i.fsf@alter.siamese.dyndns.org>
Junio,
Thanks for the assistance. I'll be looking in the direction of what
could have caused sanity problems in the upstream repo. If it happens
again and we can collect more tea leaves (this checkout was cleaned up
before I could get a copy of it to do further diagnosis :-/) I'll see
what else we can find out.
Rick
On Mon, Feb 28, 2011 at 6:25 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Rick Bradley <rick@rickbradley.com> writes:
>
>> So I have a git repo that is shallow cloned:
>>
>> % git clone --depth 1 <repo url>
>>
>> Sometimes (very rarely), when I do a branch fetch to update that
>> repository I get an error:
>>
>> % git fetch origin +refs/head/<branch>:refs/remotes/origin/<branch>
>>
>> fatal: did not find object for shallow <hash>
>
> The message comes from the repository you are fetching from. When you
> fetch from a shallow clone, the fetch process on your end tells the other
> side what commits your incomplete history ends at, and if the other end
> does not have any of these commits, you get that message. So the only
> case (unless there is a bug---and I don't think this codepath is heavily
> exercised so it is very possible there are bugs) you would see that
> message is if the other side rewound the branch and then later garbage
> collection lost the commit.
>
next prev parent reply other threads:[~2011-03-01 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 0:12 problem with updating a shallow clone via a branch fetch Rick Bradley
2011-03-01 0:25 ` Junio C Hamano
2011-03-01 2:07 ` Rick Bradley [this message]
2012-01-13 4:09 ` Rahul Jain
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=AANLkTimSRG+UkD1vJszUf+3j0nV+_pPWSE3N2Dy9SfTa@mail.gmail.com \
--to=rick@rickbradley.com \
--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 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).