From: lm@bitmover.com (Larry McVoy)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Linux Kernel Subversion Howto
Date: Wed, 2 Feb 2005 19:34:59 -0800 [thread overview]
Message-ID: <20050203033459.GA29409@bitmover.com> (raw)
In-Reply-To: <200502030028.j130SNU9004640@terminus.zytor.com>
(Thanks for the forward, Peter, I would have missed this).
Intel has very kindly donated one of their high end boxes and that's
what is running bkbits.net these days. We could run the exporter there
pretty much as often as you want. Send some love to Intel, this box is
way more stable than the previous bkbits.net. Len Brown made it happen.
As Peter said, we do exports from Linus' tree every 24 hours. I can
think of two things that we could do which might be useful to the non BK
users: export more frequently (pretty questionable in my mind but it's
no big deal to bump it up to twice or whatever) and/or export other trees
(far more interesting in my mind).
We can always use more hardware if someone is looking to donate but
we can also afford to buy what we need. Our biggest ongoing cost in
supporting you these days is our internet connection, that's running
about $11K/year for the portion that is exclusively yours. Fear not,
we get marketing value from providing that so it's no problem, we'll
keep doing it. A question though, is anyone feeling like we need to
allocate more bandwidth or is that enough? You guys currently keep a
T1 line pretty much filled 24x7, we can add another one or bump it up
to a T3 if really need to do so.
We're always looking for more ways to help you (or more properly said:
more ways to be perceived as helping) so let us know what you would like.
In Bk or out of it. Is BK/Web good enough? Need something? Let us
know.
Cheers,
--lm
On Wed, Feb 02, 2005 at 04:28:23PM -0800, H. Peter Anvin wrote:
> Followup to: <20050202155403.GE3117@crusoe.alcove-fr>
> By author: Stelian Pop <stelian@popies.net>
> In newsgroup: linux.dev.kernel
> >
> > Hi,
> >
> > I've played lately a bit with Subversion and used it for managing
> > the kernel sources, using Larry McVoy's bk2cvs bridge and Ben Collins'
> > bkcvs2svn conversion script.
> >
> > Since there is little information on the web on how to properly
> > set up a SVN repository and use it for tracking the latest kernel
> > tree, I wrote a small howto (modeled after the bk kernel howto)
> > in case it can be useful for other people too.
> >
> > Feel free to comment on it (but let's not start a new BK flamewar
> > or SVN bashing session please). If there is enough interest I'll
> > submit a patch to include this in the kernel Documentation/
> > directory.
> >
> > I've put it also on my web page along with the necessary scripts:
> > http://popies.net/svn-kernel/
> >
> > And now a question to Larry and whoever else is involved in the
> > bkcvs mirror on kernel.org: what is the periodicity of the CVS
> > repository update ?
> >
>
> Currently it's nightly. Larry has offered to run it more often if
> someone can provide a dedicated fast machine to run it on. (Larry: is
> it a matter of memory or of CPU or both? If nothing else we should
> have the old kernel.org server, dual P3/1133 with 6 GB RAM, coming
> free soon.)
>
> Please let me know if there is something that should be put on
> kernel.org; we can host repositories there of course.
>
> -hpa
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2005-02-03 16:45 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 15:54 [RFC] Linux Kernel Subversion Howto Stelian Pop
2005-02-02 16:15 ` Lethalman
2005-02-02 16:37 ` Lethalman
2005-02-03 10:34 ` Stelian Pop
2005-02-02 21:47 ` Daniele Venzano
2005-02-03 10:45 ` Stelian Pop
2005-02-04 20:04 ` Daniele Venzano
2005-02-04 20:52 ` Olaf Dietsche
2005-02-09 5:19 ` Kevin Puetz
2005-02-09 8:58 ` Miles Bader
2005-02-09 13:44 ` David Roundy
2005-02-03 0:29 ` H. Peter Anvin
2005-02-03 10:24 ` Stelian Pop
[not found] ` <200502030028.j130SNU9004640@terminus.zytor.com>
2005-02-03 3:34 ` Larry McVoy [this message]
2005-02-03 16:45 ` H. Peter Anvin
2005-02-03 19:32 ` Stelian Pop
2005-02-03 20:20 ` Larry McVoy
2005-02-03 22:00 ` Stelian Pop
2005-02-03 22:28 ` Larry McVoy
2005-02-04 13:01 ` Stelian Pop
2005-02-04 16:06 ` Larry McVoy
2005-02-04 16:22 ` Roland Dreier
2005-02-04 21:53 ` Stelian Pop
2005-02-04 17:03 ` Stelian Pop
2005-02-04 18:39 ` Larry McVoy
2005-02-04 20:05 ` Stelian Pop
2005-02-04 20:11 ` Larry McVoy
2005-02-04 21:40 ` Stelian Pop
2005-02-04 23:31 ` Francois Romieu
2005-02-05 19:38 ` Stelian Pop
2005-02-05 23:38 ` Larry McVoy
2005-02-08 15:43 ` Stelian Pop
2005-02-08 15:58 ` Larry McVoy
2005-02-08 17:17 ` Roman Zippel
2005-02-08 18:16 ` Larry McVoy
2005-02-08 18:52 ` Roman Zippel
2005-02-09 0:07 ` Theodore Ts'o
2005-02-09 2:05 ` Roman Zippel
2005-02-09 2:24 ` Jon Smirl
2005-02-09 2:35 ` Roman Zippel
2005-02-09 2:39 ` Larry McVoy
2005-02-09 2:47 ` Roman Zippel
2005-02-09 3:40 ` Larry McVoy
[not found] ` <Pine.LNX.4.61.0502091128070.7836@localhost.localdomain>
2005-02-09 17:38 ` Jon Smirl
2005-02-09 18:24 ` Nicolas Pitre
2005-02-09 18:48 ` Jon Smirl
2005-02-09 23:31 ` Roman Zippel
2005-02-09 23:52 ` Jon Smirl
2005-02-09 23:22 ` Roman Zippel
2005-02-10 0:13 ` Larry McVoy
2005-02-10 19:34 ` d.c
2005-02-11 8:40 ` Stelian Pop
2005-02-09 2:40 ` Jon Smirl
2005-02-09 2:57 ` Roman Zippel
2005-02-09 3:03 ` Jon Smirl
2005-02-09 5:48 ` Gene Heskett
2005-02-09 9:05 ` Miles Bader
2005-02-09 7:06 ` Alexandre Oliva
2005-02-09 14:48 ` d.c
2005-02-09 15:51 ` Larry McVoy
2005-02-09 17:30 ` Nicolas Pitre
2005-02-09 17:44 ` Valdis.Kletnieks
2005-02-10 5:44 ` Horst von Brand
2005-02-10 9:36 ` Alexandre Oliva
2005-02-10 21:17 ` Larry McVoy
2005-02-11 9:02 ` Stelian Pop
2005-02-11 15:30 ` Alexandre Oliva
2005-02-11 15:48 ` Larry McVoy
2005-02-11 16:18 ` Larry McVoy
2005-02-11 16:54 ` Alexandre Oliva
2005-02-11 16:13 ` Jon Smirl
2005-02-11 17:22 ` Alexandre Oliva
2005-02-11 20:00 ` Larry McVoy
[not found] ` <20050210222403.GA5920@thunk.org>
[not found] ` <or650z6syt.fsf@livre.redhat.lsd.ic.unicamp.br>
2005-02-11 15:53 ` Larry McVoy
2005-02-11 17:24 ` Alexandre Oliva
2005-02-10 5:47 ` James Bruce
2005-02-06 16:40 ` Roman Zippel
2005-02-06 17:39 ` Larry McVoy
2005-02-07 1:45 ` Roman Zippel
2005-02-07 2:10 ` Larry McVoy
2005-02-08 14:57 ` Roman Zippel
2005-02-08 15:19 ` Larry McVoy
2005-02-08 15:24 ` Stelian Pop
2005-02-08 15:47 ` Larry McVoy
2005-02-08 15:36 ` Catalin Marinas
2005-02-08 15:58 ` Jon Smirl
2005-02-08 16:15 ` Roman Zippel
2005-02-08 17:17 ` Valdis.Kletnieks
2005-02-08 17:23 ` Roman Zippel
2005-02-08 17:01 ` Larry McVoy
2005-02-07 2:16 ` Al Viro
2005-02-04 10:18 ` Michael S. Tsirkin
2005-02-04 10:59 ` Stelian Pop
2005-02-04 11:08 ` Michael S. Tsirkin
2005-02-04 11:20 ` Stelian Pop
-- strict thread matches above, loose matches on Subject: below --
2005-02-09 18:46 Larry McVoy
2005-02-09 20:13 ` Nicolas Pitre
2005-02-09 23:53 ` Larry McVoy
2005-02-10 0:14 ` Roman Zippel
2005-02-10 0:50 ` Larry McVoy
2005-02-10 9:52 ` Roman Zippel
2005-02-10 10:11 ` linux
2005-02-10 6:08 ` James Bruce
2005-02-10 15:14 ` Stelian Pop
2005-02-10 16:42 Steve Lee
2005-02-10 19:23 ` Vojtech Pavlik
2005-02-10 19:50 ` Dmitry Torokhov
2005-02-11 18:56 none given
2005-02-11 19:50 ` Larry McVoy
[not found] <fa.hd724f5.h36q2j@ifi.uio.no>
2011-08-18 19:08 ` lucasrangit
2011-08-18 19:22 ` Randy Dunlap
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=20050203033459.GA29409@bitmover.com \
--to=lm@bitmover.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