From owner-cvs-ports@FreeBSD.ORG Mon Nov 29 18:35:38 2010 Return-Path: Delivered-To: cvs-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA57F10656A4 for ; Mon, 29 Nov 2010 18:35:38 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id 725148FC14 for ; Mon, 29 Nov 2010 18:35:38 +0000 (UTC) Received: (qmail 31700 invoked by uid 399); 29 Nov 2010 18:35:37 -0000 Received: from localhost (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 29 Nov 2010 18:35:37 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4CF3F277.2070202@FreeBSD.org> Date: Mon, 29 Nov 2010 10:35:35 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101028 Thunderbird/3.1.6 MIME-Version: 1.0 To: Alexey Dokuchaev References: <201011290629.oAT6TD4u084226@repoman.freebsd.org> <20101129071448.GA56903@FreeBSD.org> <20101129075125.GA58770@FreeBSD.org> In-Reply-To: <20101129075125.GA58770@FreeBSD.org> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Wen Heping , cvs-ports@freebsd.org, cvs-all@freebsd.org, ports-committers@freebsd.org Subject: Re: cvs commit: ports/Mk bsd.python.mk ports/lang/python27 Makefile distinfo pkg-plist ports/lang/python27/files patch-Lib-test-test_socket.py patch-Lib-test-test_threading.py patch-Lib_test_test_threading.py X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2010 18:35:39 -0000 On 11/28/2010 23:51, Alexey Dokuchaev wrote: > My point is that once file is in CVS, we should try to use it even if > the name is not perfectly in line with standard scheme. The rationale > behind this rule is roughly the same as why we are not renaming existing > `patch-xy' patches or patches containing ::, for example. One could make the argument that this would be one point in favor of moving the ports repo to svn, since 'svn mv' is basically free. Moving to svn would also eliminate the related problem of repo-copies. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/