From owner-freebsd-current@FreeBSD.ORG Sun Apr 5 17:35:48 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85DD4106566B for ; Sun, 5 Apr 2009 17:35:48 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail8.sea5.speakeasy.net (mail8.sea5.speakeasy.net [69.17.117.10]) by mx1.freebsd.org (Postfix) with ESMTP id 656CD8FC18 for ; Sun, 5 Apr 2009 17:35:48 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: (qmail 32117 invoked from network); 5 Apr 2009 17:35:48 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail8.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 5 Apr 2009 17:35:47 -0000 Message-ID: <49D8EC20.70700@telenix.org> Date: Sun, 05 Apr 2009 13:36:32 -0400 From: Chuck Robey User-Agent: Thunderbird 2.0.0.19 (X11/20090121) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: comparing svn and cvs somewhat X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Apr 2009 17:35:48 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have gotten a local copy of the svn repo going on my home here, by using svnsync, which seems (by what I've read and been told) to be the right method. I'm wondering about a feature that is there for cvs, in cvsup, but which seems to be missing in svnsync for svn. What I'm after is a much better way to maintain a local repo than what I'm seeing now in maintaining my svn repo, with svnsync. The main feature that I think I'm missing is the ability to be able to compare files on a central server (something serving all FreeBSDers) to files on everybody's personal repo, and to automatically update them if there isn't a perfect comparison. I'm not talking about the varying ways that your repo might get damaged, but I think that svnsync only knows that you have a particular revision number, not that the file is correct. If your repo gets damage, I think that nothing exists to automatically fix it. So, if this feature IS something that's already available in svn, I'd like to here a summary of what tool to use the how to do it, so I can verify myself that what I'm thinking about already exists. That'd free me to begin writing software, to see if I could implement such a feature. I'm not truly certain of this, but it seems to me that implementing such a feature, using something like Python, would be very easy to do. Could end up with a svn version of cvs's cvsup. Maybe, call it svnup? I'm terrible at names, if you think that name makes no sense, please, tell me so. Second question, maybe a more difficult one, I wonder if such a feature would be a popular one, or perhaps, something extremely outside of the way that we would want our repo's to be maintained? Maybe FreeBSD doesn't want to allow folks to have their own repos? I think that this ability, to make sure that your home repo is correct, is missing now for svn, I need to know if this is right, and that if the ability suddenly showed up, would that be a Good Thing or a Bad Thing? Whatever, it seems like a very fun thing to write, I hope it's not already written. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknY7CAACgkQz62J6PPcoOk7NACfZ5pnVZcdOSFj/MKYOGe+PtUy BjYAn2sjL9AURZXf/hFXN08hXUuZtCp1 =05rB -----END PGP SIGNATURE-----