From: Theodore Tso <tytso@mit.edu>
To: Shen Feng <shen@cn.fujitsu.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: git-clone problem
Date: Fri, 13 Jun 2008 11:43:18 -0400 [thread overview]
Message-ID: <20080613154318.GF24675@mit.edu> (raw)
In-Reply-To: <48522544.50306@cn.fujitsu.com>
On Fri, Jun 13, 2008 at 03:44:04PM +0800, Shen Feng wrote:
> Hello,
>
> When I try to clone the ext4 development tree, I got the following error.
> Is there anything wrong?
>
> [fenian@localhost ~]$ git-clone http://www.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
Dont use the http transport; it's not very efficient, and often
breaks. I've fixed it for now (the hook to automatically run "git
update-server-info" was missing), but you'll get much faster and more
reliable results if you clone via the URL:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
Actually the best thing to do is if you already have a local
repository of the kernel, to do:
git clone -s my-clone-of-linus-tree ext4
The edit the .git/config file so the url for [remote "master"] is:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
... and do a "git pull". This will be much more efficient since you
limit the amount of data that you have to pull down over the network.
Note that the ext4 patch queue tends to have a much more dynamic and
bleeding-edge set of patches than the ext4 git tree. The ext4 patch
queue is a quilt patch series maintained at this git repository:
git://repo.or.cz/ext4-patch-queue.git
- Ted
prev parent reply other threads:[~2008-06-13 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 7:44 git-clone problem Shen Feng
2008-06-13 15:43 ` Theodore Tso [this message]
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=20080613154318.GF24675@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=shen@cn.fujitsu.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.