From: Dirk Behme <dirk.behme@de.bosch.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: 1dfcfbce2d643b7c7b56dc828f36ced9de2bf9f2
Date: Mon, 22 Aug 2005 10:11:19 +0200 [thread overview]
Message-ID: <430988A7.60906@de.bosch.com> (raw)
In-Reply-To: <7vpss6bel3.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Dirk Behme <dirk.behme@de.bosch.com> writes:
>
>
>>Seems to me that this breaks http update
>>
>>cg-update http://www.kernel.org/pub/scm/git/git.git
>>
>>error: Tried
>>http://www.kernel.org/pub/scm/git/git.git/objects/6f/f87c4664981e4397625791c8ea3bbb5f2279a3
>>Cannot obtain needed blob 6ff87c4664981e4397625791c8ea3bbb5f2279a3
>>while processing commit 1dfcfbce2d643b7c7b56dc828f36ced9de2bf9f2.
>>cg-pull: objects pull failed
>
>
> I suspect that your copy of Cogito/git is old and incapable of
> fetching from a packed repository. Did your Cogito come with
> its own copy of git (specifically, git-http-pull)? Modern
> Cogito "cg-pull" uses git-http-pull from core GIT as its
> underlying pull driver for http transport, which should not have
> the problem anymore.
My cogito source directory has no git* files any more. I update directly
from git.git and cogito.git. Last time this was done last week
(wednesday, thursday?). Is this old? I have no problems with cg-update
using http of cogito.git. I think cogito.git uses packed repository as well?
Many thanks
Dirk
next prev parent reply other threads:[~2005-08-22 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 18:49 1dfcfbce2d643b7c7b56dc828f36ced9de2bf9f2 Junio C Hamano
2005-08-22 6:06 ` 1dfcfbce2d643b7c7b56dc828f36ced9de2bf9f2 Dirk Behme
2005-08-22 7:44 ` 1dfcfbce2d643b7c7b56dc828f36ced9de2bf9f2 Junio C Hamano
2005-08-22 8:11 ` Dirk Behme [this message]
2005-08-23 1:07 ` 1dfcfbce2d643b7c7b56dc828f36ced9de2bf9f2 Junio C Hamano
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=430988A7.60906@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.