From: Sergey Vlasov <vsu@altlinux.ru>
To: Bryan O'Sullivan <bos@serpentine.com>
Cc: Erik Mouw <erik@harddisk-recovery.com>, git@vger.kernel.org
Subject: Re: Problem with clone hanging
Date: Mon, 7 Aug 2006 21:52:01 +0400 [thread overview]
Message-ID: <20060807215201.b54da1ce.vsu@altlinux.ru> (raw)
In-Reply-To: <1154971295.26375.48.camel@sardonyx>
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
On Mon, 07 Aug 2006 10:21:35 -0700 Bryan O'Sullivan wrote:
> On Mon, 2006-08-07 at 19:12 +0200, Erik Mouw wrote:
>
> > Looks like the same problem that kernel.org used to have. The other
> > side probably runs git-1.4.0, they should upgrade to 1.4.1.
>
> OK, thanks for the helpful response.
>
> > In the mean
> > time, you could clone using http and later on switch to git transport.
>
> It seems like Mellanox doesn't publish that repository over HTTP, so I'm
> stuck. Tziporet, can you upgrade your git installation, please?
In the meantime, you can try to specify a local clone of the mainline
Linux repository with the --reference=... option to git-clone. Then
the server will need to send only objects which do not exist in the
mainline tree, and should be able to prepare the pack faster.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2006-08-07 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 16:42 Problem with clone hanging Bryan O'Sullivan
2006-08-07 17:12 ` Erik Mouw
2006-08-07 17:21 ` Bryan O'Sullivan
2006-08-07 17:52 ` Sergey Vlasov [this message]
2006-08-07 18:23 ` Bryan O'Sullivan
2006-08-07 18:32 ` Sergey Vlasov
2006-08-07 20:05 ` Michael S. Tsirkin
2006-08-07 22:26 ` Bryan O'Sullivan
-- strict thread matches above, loose matches on Subject: below --
2006-08-07 18:57 Tziporet Koren
2006-08-07 19:41 ` Michael S. Tsirkin
2006-08-07 22:34 ` Bryan O'Sullivan
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=20060807215201.b54da1ce.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--cc=bos@serpentine.com \
--cc=erik@harddisk-recovery.com \
--cc=git@vger.kernel.org \
/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.