From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: BK->CVS is live
Date: Mon, 17 Mar 2003 16:58:45 +0100 [thread overview]
Message-ID: <20030317155845.GH17073@lug-owl.de> (raw)
In-Reply-To: <200303171552.h2HFqK907234@work.bitmover.com>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Mon, 2003-03-17 07:52:20 -0800, Larry McVoy <lm@bitmover.com>
wrote in message <200303171552.h2HFqK907234@work.bitmover.com>:
> I think those repositories are stable enough you can start to count on
> them. Sam and others have looked over their changes and think that
> the CVS tree has accurate data.
>
> The CVS repository is at
>
> cvs -d:pserver:anonymous@kernel.bkbits.net:/home/cvs
>
> and it has two top level directories, linux-2.4 and linux-2.5.
jbglaw@mirror:~$ rsync kernel.bkbits.net::
rsync: failed to connect to kernel.bkbits.net: Connection refused
rsync error: error in socket IO (code 10) at clientserver.c(83)
:-(
Allowing rsync on the repository could help people on slow links (modem)
esp. as CVS isn't exactly known to be fast and evvective. I'd love to
have it rsyncable (as we have it for mips-linux:-)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-03-17 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 15:52 Larry McVoy
2003-03-17 15:58 ` Jan-Benedict Glaw [this message]
2003-03-17 16:11 ` David Woodhouse
2003-03-17 17:02 ` Sebastian D.B. Krause
2003-03-17 17:03 ` Tomas Szepe
2003-03-17 18:12 ` Shawn
2003-03-17 18:16 ` Shawn
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=20030317155845.GH17073@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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
all inboxes | Powered by JetHome®