lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 13 Jun 2008 11:43:18 -0400
From:	Theodore Tso <>
To:	Shen Feng <>
Subject: Re: git-clone problem

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@...alhost ~]$ git-clone

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:


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:


... 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:


	      	     	     	      	       - Ted
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists