From owner-freebsd-stable@FreeBSD.ORG Sat Jun 28 10:01:06 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FE7037B401 for ; Sat, 28 Jun 2003 10:01:06 -0700 (PDT) Received: from smtp.eos.ocn.ne.jp (eos.ocn.ne.jp [211.6.83.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F54844001 for ; Sat, 28 Jun 2003 10:01:05 -0700 (PDT) (envelope-from hrs@eos.ocn.ne.jp) Received: from mail.d.allbsd.org (p19167-adsao12honb4-acca.tokyo.ocn.ne.jp [219.165.47.167]) by smtp.eos.ocn.ne.jp (Postfix) with ESMTP id 7F4043F34; Sun, 29 Jun 2003 02:01:04 +0900 (JST) Received: from localhost (alph.allbsd.org [192.168.0.10]) h5SH0QSI048919; Sun, 29 Jun 2003 02:00:27 +0900 (JST) (envelope-from hrs@eos.ocn.ne.jp) Date: Sun, 29 Jun 2003 01:56:47 +0900 (JST) Message-Id: <20030629.015647.122577658.hrs@eos.ocn.ne.jp> To: sam@rfc1149.net From: Hiroki Sato In-Reply-To: <87adc2p2rq.fsf@inf.enst.fr> References: <20030624.185717.63135353.hrs@eos.ocn.ne.jp> <20030624123946.L81056@fubar.adept.org> <87adc2p2rq.fsf@inf.enst.fr> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 3.2 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: IPv6 CVSUP mirrors? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2003 17:01:06 -0000 Samuel Tardieu wrote in <87adc2p2rq.fsf@inf.enst.fr>: sam> It would be great. However, from what I've seen on cvsync, it lacks sam> the "checkout" feature of CVSup (the ability to use cvsup to checkout sam> only a branch, such as the HEAD, a fast "cvs update"). Or did I sam> overlook something? You are right. cvsync does not have checkout mode at this moment, but the author is planning to implement it (and rsync algorithm). Stay tuned. -- | Hiroki SATO /