lists.openwall.net   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] [thread-next>] [day] [month] [year] [list]
Message-ID: <9e4733910707221717u2ce828ccsc7cc5812d129dfc9@mail.gmail.com>
Date:	Sun, 22 Jul 2007 20:17:56 -0400
From:	"Jon Smirl" <jonsmirl@...il.com>
To:	"Michael Tharp" <gxti@...tiallystapled.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	"Git Mailing List" <git@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Git tree for old kernels from before the current tree

On 7/22/07, Michael Tharp <gxti@...tiallystapled.com> wrote:
> H. Peter Anvin wrote:
> > Wouldn't be hard to make a git tree with all the patches all the way
> > back to 0.01 even...
>
> It'd be delightful from a completeness standpoint (and I do love
> completeness), but considering it already takes a good 20 minutes to
> clone the 2.6 tree over a respectable cable connection, I'd have to
> object on the grounds of size. Now, if it was kept off in its own tree
> for people who don't mind ravaging kernel.org resources to satisfy their
> own curiosity, that's fine too.

git has an extremely effective diffing mechanism. You may surprised at
how little it adds.
For example, git compressed the 2.6GB mozilla cvs tree down to 400MB.

I used to clone trees all the time, but now I'm much better at using
git and I haven't cloned a complete tree from kernel.org in a year.
git remote is a cool feature.

-- 
Jon Smirl
jonsmirl@...il.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ