From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Michael Tharp" <gxti@partiallystapled.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"Git Mailing List" <git@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Git tree for old kernels from before the current tree
Date: Sun, 22 Jul 2007 20:17:56 -0400 [thread overview]
Message-ID: <9e4733910707221717u2ce828ccsc7cc5812d129dfc9@mail.gmail.com> (raw)
In-Reply-To: <46A3E7BA.6030609@partiallystapled.com>
On 7/22/07, Michael Tharp <gxti@partiallystapled.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@gmail.com
next prev parent reply other threads:[~2007-07-23 0:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 20:49 Git tree for old kernels from before the current tree Jon Smirl
2007-07-22 21:00 ` Jan Engelhardt
2007-07-22 21:13 ` Paul Mundt
2007-07-22 21:46 ` Jan Engelhardt
2007-07-22 22:00 ` Jan Engelhardt
2007-07-22 22:10 ` H. Peter Anvin
2007-07-22 23:26 ` Michael Tharp
2007-07-23 0:17 ` Jon Smirl [this message]
2007-07-23 16:55 ` Linus Torvalds
2007-07-23 17:48 ` Nicolas Pitre
2007-07-23 18:02 ` Linus Torvalds
2007-07-23 19:06 ` Nicolas Pitre
2007-07-23 20:10 ` Linus Torvalds
2007-07-23 20:45 ` Nicolas Pitre
2007-07-23 23:11 ` Arjan van de Ven
2007-07-23 23:46 ` Al Viro
2007-07-23 23:49 ` H. Peter Anvin
2007-07-24 0:10 ` Nicolas Pitre
2007-07-24 0:12 ` H. Peter Anvin
2007-07-24 0:36 ` Nicolas Pitre
2007-08-20 20:09 ` Jan-Benedict Glaw
2007-08-20 20:46 ` Nicolas Pitre
2007-09-19 1:19 ` Oleg Verych
2007-07-23 18:57 ` Theodore Tso
2007-07-23 19:08 ` Nicolas Pitre
2007-07-23 19:44 ` Linus Torvalds
2007-07-23 20:22 ` Theodore Tso
2007-07-23 0:00 ` Jon Smirl
2007-08-19 19:24 ` Git tree for old kernels Nicolas Pitre
2007-08-20 17:16 ` Josef Sipek
2007-08-20 17:40 ` Nicolas Pitre
2007-08-20 18:01 ` Josef Sipek
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=9e4733910707221717u2ce828ccsc7cc5812d129dfc9@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=gxti@partiallystapled.com \
--cc=hpa@zytor.com \
--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;
as well as URLs for NNTP newsgroup(s).