public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.71
Date: Sat, 14 Jun 2003 17:21:53 -0700	[thread overview]
Message-ID: <20030615002153.GA20896@work.bitmover.com> (raw)

Linus said:
> I think I'll call this kernel the "sticky turtle", in honor of that 
> historic "greased weasel" kernel, and as a comment on how sadly dependent 
> I've become on the daily BK snapshots. It's been too long since 2.5.70.

I think more releases are good but for the snapshot people...

There are multiple options:

	bk pull bk://linux.bkbits.net/linux-2.5
	cvs -d:pserver:anonymous@kernel.bkbits.net:/home/cvs co linux-2.5

and Ben Collins is working on a bkSVN gateway (it's actually a
BK->CVS->SVN but whatever) so that will be an option soon as well.  Huh,
while I'm thinking about it since we're hosting the CVS tree there is no
good reason not to host the SVN tree as well, I have to believe that SVN
uses less bandwidth than CVS (please, say it's so).  Ben, send me or Davem
an ssh2 key and we'll set you up with an account on kernel.bkbits.net.
This isn't some advertising ploy so feel free to make some DNS entry which
points there, like svn.kernel.org, and then there is no BK in the picture.
HPA can help you with that.  In fact, hpa, weren't we going to make a 
cvs.kernel.org?  If so, how about pointing that at kernel.bkbits.net for
the time being and then if someone steps forward to host that you can
just change the DNS entry?
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

             reply	other threads:[~2003-06-15  0:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-15  0:21 Larry McVoy [this message]
2003-06-17 16:13 ` Linux 2.5.71 H. Peter Anvin
2003-06-18  1:39   ` SCM domains [was Re: Linux 2.5.71] Larry McVoy
2003-06-18  1:55     ` H. Peter Anvin
2003-06-18  1:14       ` Ben Collins
2003-06-18  4:11         ` H. Peter Anvin
2003-06-18  4:35           ` Larry McVoy
2003-06-19 20:36             ` Bill Davidsen
2003-06-19 20:39             ` Bill Davidsen
2003-06-20  0:53               ` H. Peter Anvin
2003-06-18 20:09           ` Ben Collins
2003-06-18  3:38       ` Larry McVoy
2003-06-18  4:02         ` Andrea Arcangeli
2003-06-19 17:44     ` Henning P. Schmiedehausen
     [not found] <20030614213012$6a47@gated-at.bofh.it>
2003-06-14 22:21 ` Linux 2.5.71 John Weber
2003-06-15  0:42   ` Herbert Xu
2003-06-15  0:43   ` Herbert Xu
2003-06-15  1:10     ` Arnaldo Carvalho de Melo
  -- strict thread matches above, loose matches on Subject: below --
2003-06-14 21:17 Linus Torvalds
2003-06-15  1:42 ` Florin Iucha
2003-06-15  1:58   ` Linus Torvalds
2003-06-15  2:00     ` Florin Iucha
2003-06-15  4:55       ` Florin Iucha
2003-06-15  8:03     ` Trond Myklebust
2003-06-15  6:54 ` Andre Hedrick
2003-06-15  7:15   ` Andre Hedrick
2003-06-15 13:29 ` Paweł Gołaszewski
2003-06-15 13:45   ` Russell King
2003-06-16 18:04 ` John Cherry

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=20030615002153.GA20896@work.bitmover.com \
    --to=lm@bitmover.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