From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5460 invoked by alias); 16 Oct 2009 14:10:12 -0000 Received: (qmail 5449 invoked by uid 22791); 16 Oct 2009 14:10:11 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from virtual.bogons.net (HELO virtual.bogons.net) (193.178.223.136) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 16 Oct 2009 14:10:07 +0000 Received: from jifvik.dyndns.org (jifvik.dyndns.org [85.158.45.40]) by virtual.bogons.net (8.10.2+Sun/8.11.2) with ESMTP id n9GEA4411465 for ; Fri, 16 Oct 2009 15:10:04 +0100 (BST) Received: from [172.31.1.126] (neelix.jifvik.org [172.31.1.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jifvik.dyndns.org (Postfix) with ESMTP id 63A853FEB; Fri, 16 Oct 2009 15:10:04 +0100 (BST) Message-ID: <4AD87EBA.5000603@jifvik.org> Date: Fri, 16 Oct 2009 14:10:00 -0000 From: Jonathan Larmour User-Agent: Mozilla Thunderbird 1.0.8-1.1.fc4 (X11/20060501) MIME-Version: 1.0 To: Alex Schuilenburg Cc: ecos-maintainers@ecos.sourceware.org Subject: Re: hg conversion notes and summary References: <4AD32231.5060506@ecoscentric.com> <4AD5E3C1.10700@ecoscentric.com> <4AD7F4D3.6010008@jifvik.org> <4AD8405D.1010205@ecoscentric.com> In-Reply-To: <4AD8405D.1010205@ecoscentric.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-maintainers-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@ecos.sourceware.org X-SW-Source: 2009-10/txt/msg00004.txt.bz2 Alex Schuilenburg wrote: > Jonathan Larmour wrote on 2009-10-16 05:21: > >>Alex Schuilenburg wrote: >>I also see an hgext dir with the same date, including bugzilla.py, >>notify.py. >> >>If we do make a decision to move to hg, we'll need to know if there >>would be any problems using that version, and so whether I'd need to >>agitate towards moving sourceware to something more recent (which >>isn't straightforward as other projects use hg too). > > It would be worthwhile upgrading IMHO to pick up the current features > and fixes - the only requirement is python 2.4 or above. Given it's used by other projects, I'd have to give a good reason for potential disruption. If there is something concrete I could mention (bug X will make it hard, or it is missing important feature Y) that would be useful. > There are no problems I know of upgrading - I upgraded from 1.0.2 to > 1.3.1 midway through our internal CVS to hg conversion and in fact > benefited from one of the bugfixes (hg reports a file as modified when > it is not - simple to recover, but annoying when you do a major merge), > but it does not matter really what sourceware is running if it is only > handling push/pull since I would assume any merge work would be done > offsite on sombody's own machine and their own updated version of hg. Shell accounts on sourceware are usually highly restricted, so yes. > That after all is what DRCS is all about ;-) The only local sourceware > issues may be bugzilla, notify or the hgwebdir.cgi which have seen > fairly useful improvements since 1.0 (including git plugin and git views > so those got fans still get the same look and feel, should you be so > inclined). Would the bugzilla plugin need to live on sourceware or on the bugzilla machine? You can defer answering till after a decision's been made :-) Jifl -- --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine