From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@linux-mips.org
Subject: Re: Kernel git repository
Date: Tue, 31 Jan 2006 08:48:05 +0100 [thread overview]
Message-ID: <20060131074805.GR18336@lug-owl.de> (raw)
In-Reply-To: <20060130210837.GA11232@linux-mips.org>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
On Mon, 2006-01-30 21:08:37 +0000, Ralf Baechle <ralf@linux-mips.org> wrote:
> As some of you have been complained - the kernel git repository has become
> rather large with it's currently slightly over 200MB. Since most users
> are not interested in the full 12 year project history I've prepared a
> second, slimmed down repository. It can be cloned at:
>
> git clone git://www.linux-mips.org/git/linux-2.6.15.git linux.git
>
> This tree is just about 62MB in size and starts at 2.6.15.
Do you intent to work on that tree? ...or keep the other one as the
"master" tree? ...or actually dump the mips-linux history and go for
Linus' tree?
The point is, really, HDD space is cheap these days. While the initial
download may be painfull, it's only 200 MB. Hell, back in those times,
I kept a Debian unstable box up'to'date with an analog modem at 28k8Bd
and that worked just fine (though it took an hour or two every day:-)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-01-31 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 21:08 Kernel git repository Ralf Baechle
2006-01-30 21:30 ` Ilya A. Volynets-Evenbakh
2006-01-31 0:52 ` Stuart Longland
2006-01-31 7:48 ` Jan-Benedict Glaw [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=20060131074805.GR18336@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@linux-mips.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 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.