From: Bill Davidsen <davidsen@tmr.com>
To: Sean <seanlkml@sympatico.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Arrr! Linux v2.6.14-rc2
Date: Wed, 21 Sep 2005 14:28:43 -0400 [thread overview]
Message-ID: <4331A65B.90103@tmr.com> (raw)
In-Reply-To: <BAYC1-PASMTP04AB35B0A82E89B341AB0BAE950@cez.ice>
Sean wrote:
> On Tue, September 20, 2005 10:25 am, Gene Heskett said:
>
>
>>Humm, what are they holding out for, more ram or more cpu?:-)
>>
>>FWIW, http://master.kernel.org doesn't show it either just now.
>
>
> Gene,
>
> While kernel.org snapshots will no doubt be working again shortly, you
> might want to consider using git. It reduces the amount you have to
> download for each release a lot.
>
> It's really easy to grab a copy of git and use it to grab the kernel:
>
> mkdir kernel
> cd kernel
> wget http://kernel.org/pub/software/scm/git/git-core-0.99.7.tar.bz2
> tar -xvjf git-core-0.99.7.tar.bz2
> cd git-core-0.99.7
> make install
> cd ..
>
> git clone \
> rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git \
> linux
>
> cd linux
> git checkout
>
>
> The above is given as an attachment as well because of annoying word wrap
> issues with the long url's. Anyway, after that you can stay current with
> the latest Linus release with a simple "git pull".
But that pulls the current tree, doesn't it? Not the git release?
For purposes of bug reporting and fixing, I would think that having some
reproducible version is superior. If I say git3, anyone can get it, it
would appear that "git pull" isn't as deterministic.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-09-21 18:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 3:22 Arrr! Linux v2.6.14-rc2 Linus Torvalds
2005-09-20 3:44 ` Nick Piggin
2005-09-20 4:50 ` Gene Heskett
2005-09-20 13:31 ` Patrick McFarland
2005-09-20 14:05 ` Gene Heskett
2005-09-20 14:10 ` Russell King
2005-09-20 14:25 ` Gene Heskett
2005-09-20 15:20 ` Sean
2005-09-20 15:20 ` Sean
2005-09-20 20:45 ` Gene Heskett
2005-09-20 20:57 ` Gene Heskett
2005-09-20 21:00 ` Matthew Dharm
2005-09-20 21:23 ` Gene Heskett
2005-09-20 21:39 ` Gene Heskett
2005-09-21 16:50 ` Gene Heskett
2005-09-21 18:28 ` Bill Davidsen [this message]
2005-09-21 19:06 ` Sean
2005-09-21 19:06 ` Sean
2005-09-20 15:29 ` Russell King
2005-09-20 15:32 ` Alexander Nyberg
2005-09-20 15:40 ` Sean
2005-09-20 15:40 ` Sean
2005-09-20 16:18 ` Jan Dittmer
2005-09-20 16:26 ` Sean
2005-09-20 16:26 ` Sean
2005-09-20 16:44 ` Jan Dittmer
2005-09-20 16:50 ` Sean
2005-09-20 16:50 ` Sean
2005-09-20 17:00 ` Jan Dittmer
2005-09-20 17:02 ` Linus Torvalds
2005-09-20 17:09 ` Sean
2005-09-20 17:09 ` Sean
2005-09-20 21:42 ` using -gitX snapshot tags [was Re: Arrr! Linux v2.6.14-rc2] Sean
2005-09-20 21:42 ` Sean
2005-09-20 17:09 ` Arrr! Linux v2.6.14-rc2 Alexey Dobriyan
2005-09-20 17:59 ` Horst von Brand
2005-09-20 18:34 ` Sean
2005-09-20 18:34 ` Sean
2005-09-20 18:48 ` Russell King
2005-09-21 0:43 ` Gene Heskett
2005-09-21 18:22 ` Bill Davidsen
2005-09-20 23:03 ` Martin J. Bligh
2005-09-20 23:11 ` Nish Aravamudan
2005-09-20 23:12 ` James Bottomley
2005-09-20 23:13 ` Martin J. Bligh
2005-09-21 22:51 ` Martin J. Bligh
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=4331A65B.90103@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
/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.