linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shachar Shemesh <linux-il@shemesh.biz>
To: Ben Collins <bcollins@debian.org>
Cc: Shachar Shemesh <lkml@shemesh.biz>,
	Larry McVoy <lm@work.bitmover.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BK->CVS, kernel.bkbits.net
Date: Sun, 20 Apr 2003 17:13:16 +0300	[thread overview]
Message-ID: <3EA2AAFC.70708@shemesh.biz> (raw)
In-Reply-To: <20030420134712.GM2528@phunnypharm.org>

Ben Collins wrote:

>If only i386 was my only development environment. Add sparc64 as my
>primary and hppa, ia64, mips, i386, arm and powerpc as secondaries.
>  
>
I don't see why that matters to you. You only need one cvsup able 
machine to sync the local repository. Once it's local, you can check out 
any tree from it using CVS as usual. There is no difference between 
cvsup and rsync in that respect. I'm not sure where and how the sparc 
tree is held, as I understand it's not in the main tree (but is it in 
the main repository?).

In any case, I'm not even sure that cvsup CAN run without an underling 
rsync server. I simply don't know. I do know that cvsup uses rsync for 
files it cannot optimize using its own algorithm.

-- 
Shachar Shemesh
Open Source integration consultant
Home page & resume - http://www.shemesh.biz/



  reply	other threads:[~2003-04-20 14:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 16:27 BK->CVS, kernel.bkbits.net Larry McVoy
2003-04-17 20:52 ` H. Peter Anvin
2003-04-20  0:30   ` Larry McVoy
2003-04-20 13:16     ` Roman Zippel
2003-04-20 15:23       ` Larry McVoy
2003-04-20 15:42         ` Roman Zippel
2003-04-21  4:46     ` Neil Brown
2003-04-21  6:58       ` Jeff Garzik
2003-04-23 15:49       ` Carl-Daniel Hailfinger
2003-04-24  2:45         ` Larry McVoy
2003-04-24  7:21           ` Christoph Hellwig
2003-04-24  9:19           ` Carl-Daniel Hailfinger
2003-04-21 15:58     ` Jamie Lokier
2003-04-20  1:34 ` Ben Collins
2003-04-20  1:49   ` Larry McVoy
2003-04-21 18:58     ` H. Peter Anvin
2003-04-21 21:41       ` Ben Collins
2003-04-20  7:32   ` Shachar Shemesh
2003-04-20  9:58     ` Geert Uytterhoeven
2003-04-20 13:47       ` Shachar Shemesh
2003-04-20 13:01     ` Ben Collins
2003-04-20 13:37       ` Shachar Shemesh
2003-04-20 13:42         ` viro
2003-04-20 13:47         ` Ben Collins
2003-04-20 14:13           ` Shachar Shemesh [this message]
2003-04-20 14:42           ` Shachar Shemesh
2003-04-20 14:47             ` Wichert Akkerman
2003-04-20 14:58               ` Shachar Shemesh
2003-04-20 15:45             ` viro
2003-04-22 11:09         ` Gerd Knorr

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=3EA2AAFC.70708@shemesh.biz \
    --to=linux-il@shemesh.biz \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@shemesh.biz \
    --cc=lm@work.bitmover.com \
    /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;
as well as URLs for NNTP newsgroup(s).