All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Shachar Shemesh <lkml@shemesh.biz>
Cc: 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 09:01:23 -0400	[thread overview]
Message-ID: <20030420130123.GK2528@phunnypharm.org> (raw)
In-Reply-To: <3EA24CF8.5080609@shemesh.biz>

On Sun, Apr 20, 2003 at 10:32:08AM +0300, Shachar Shemesh wrote:
> Ben Collins wrote:
> 
> >I hate asking this on top of the work you already provide, but would it
> >be possible to allow rsync access to the repo itself? I have atleast 6
> >computers on my LAN where I keep source trees (2.4 and 2.5), and it
> >would be much less b/w on my metered T1 and on your link aswell if I
> >could rsync one main "mirror" of the cvs repo and then point all my
> >machines at it.
> >
> There is a better tool (for this particular task), called "cvsup". It 
> does a wonderful job of keeping cvs repositories in synch. I realize I 
> just asked for a THIRD tool, so it should only go in if the admins are 
> willing to take care of it.

How does cvsup help when I have 6 copies of two different repositories
on my side and I only want to hit the other side one time to update all
6 copies?

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/

  parent reply	other threads:[~2003-04-20 13:00 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 [this message]
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
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=20030420130123.GK2528@phunnypharm.org \
    --to=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 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.