From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: devzero@web.de, Chris Mason <chris.mason@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with git.kernel.org
Date: Mon, 15 Dec 2008 14:15:14 +0100 [thread overview]
Message-ID: <49465862.9090400@s5r6.in-berlin.de> (raw)
In-Reply-To: <543076374@web.de>
devzero@web.de wrote:
[I wrote]
>> The kernel repo is more than 100 times as big as this emerald repo, 400
>> times as big perhaps.
>
> yes, but http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-unstable-standalone.git
> is a small repository, just containing the btrfs driver.
Right, I missed that.
...
>> Try to download with git.
>
> i did, but it didn`t work either. i`m behind a http proxy.
Right again,
$ git clone \
http://www.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable-standalone.git
fails here after a few objects with
Cannot obtain needed blob ca442d313d86dc67e0a2e5d584b465bd382cbf5c
while processing commit 96dd95de14c77309abd2521d06c4825162b85e0a.
fatal: Fetch failed.
Chris, you should enable fetching over http by
$ cd /pub/scm/linux/kernel/git/mason/btrfs-unstable-standalone.git
$ cp -p hooks/post-update.sample hooks/post-update
Also run git-update-server-info unless you are pushing something soon
again anyway.
Cloning a full kernel repo over http may be too unreliable, but cloning
a smaller repo like the btrfs standalone repo should work acceptably
over http.
--
Stefan Richter
-=====-==--- ==-- -====
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-12-15 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 12:42 devzero
2008-12-15 13:15 ` Stefan Richter [this message]
2008-12-15 16:07 ` Sitaram Chamarty
2008-12-16 12:10 ` Stefan Richter
2008-12-15 20:54 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2008-12-15 9:22 devzero
2008-12-15 10:22 ` Stefan Richter
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=49465862.9090400@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=chris.mason@oracle.com \
--cc=devzero@web.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®