From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30971 invoked by alias); 27 Oct 2009 15:09:18 -0000 Received: (qmail 30962 invoked by uid 22791); 27 Oct 2009 15:09:17 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 27 Oct 2009 15:09:13 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id C4FD22F78559; Tue, 27 Oct 2009 15:09:11 +0000 (GMT) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nNdjNzpdEpo1; Tue, 27 Oct 2009 15:09:10 +0000 (GMT) Message-ID: <4AE70D12.5010405@ecoscentric.com> Date: Tue, 27 Oct 2009 15:09:00 -0000 From: Alex Schuilenburg User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Jonathan Larmour 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> <4AD87EBA.5000603@jifvik.org> <4AD903A4.7000800@ecoscentric.com> In-Reply-To: <4AD903A4.7000800@ecoscentric.com> Content-Type: text/plain; charset=ISO-8859-1 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/msg00007.txt.bz2 Hi Jifl, Just another couple of updates: Alex Schuilenburg wrote on 2009-10-17 00:37: > Jonathan Larmour wrote: > > [...] >>> 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? >> > Not on the bugzilla machine, and given restricted shell access, not on > sourceware either. > [...] I have changed my mind on this and switched from using email to provide bugzilla comments to using hg-bugzilla itself. I found the email interface has potential for pitfalls in user hg configury (smtp agent, email address used/conversion/etc) when mixing with the patchbomb extension, and anyway, what was I thinking - it is all distributed so can be handled by anyone ;-) eCosCentric will be maintaining an internal copy of the repository anyway, so everything is configured on our hosts for bugzilla comments. Nobody else needs to install anything, other than eCosCentric which provides the bugzilla database anyway (and it is already installed). The bugzilla comment will get added each time eCosCentric pulls in changes from sourceware. This is live now on eCosCentric repos and I can make it live now on sourceware for you to test. I just need to uncomment a single line. That is, any CVS checkin or hg commit with "bug #" in the commit message will result in a comment being added to the bug in the bugzilla database. The comment will appear to have been made by the person making the commit, with links back to the repo, and the usual bugzilla hooks (email etc) will follow. The whole comment is fully customisable so I have just used the one in the hg book, which was better imho than the default. The only additional configury was the mapping of checkin name to bugzilla name, which I have done for all the known maintainers. Apologies also for spamming, ecos-bugs@ecos.sourceware.org. I was testing email notification as well as bugzilla comments using pulls and forgot to uncomment the placeholder email notification. -- Alex Schuilenburg Managing Director/CEO eCosCentric Limited www.ecoscentric.com