Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29847 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32204 invoked by uid 1010); 28 May 2007 16:51:44 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 32182 invoked from network); 28 May 2007 16:51:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 May 2007 16:51:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.132.244 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.132.244 an-out-0708.google.com Received: from [209.85.132.244] ([209.85.132.244:4110] helo=an-out-0708.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/11-47763-E980B564 for ; Mon, 28 May 2007 12:51:43 -0400 Received: by an-out-0708.google.com with SMTP id c18so428765anc for ; Mon, 28 May 2007 09:51:38 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TVsB2XtJUnawnyWmnJfqfQujcxumgY366Z3yzBZa8Wmt5vGnEZ4rv9SK2KA5oJnffQvWRIYtXlan4LT8Adb382lAkY4v7Gwa+iMWsRQQUdXttYrFrgXVY48Vwvy97K4euN4g8w33P9/XB+mUDNKGHT4mvKOEI0fTt5fTPZCO6nU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sCb65XnNO9RBv1lt+z6nGVWG3UmTnX9O8yrWqfDpZgTqAtIPyZ6fs6ykB99kiXKg9f5sXC28XRbfuNirUj+kifS906SNVOcutdZQj6d2zOlbN62qX8EYJNLmndtQbX5nU4hn6zz5H2m+PkAB48avrc1ggiNAEDkN6anJFrHUEUo= Received: by 10.114.134.1 with SMTP id h1mr3032068wad.1180371097170; Mon, 28 May 2007 09:51:37 -0700 (PDT) Received: by 10.114.178.2 with HTTP; Mon, 28 May 2007 09:51:36 -0700 (PDT) Message-ID: Date: Mon, 28 May 2007 18:51:36 +0200 To: "Wez Furlong" Cc: "Ilia Alshanetsky" , "Edin Kadribasic" , "PHP Internals List" In-Reply-To: <4e89b4260705280856t47429e54ofcc182e02a6627e5@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4e89b4260705280856t47429e54ofcc182e02a6627e5@mail.gmail.com> Subject: Re: [PHP-DEV] better changeset tracking From: pierre.php@gmail.com (Pierre) Sorry for my initial offlist reply. My evil gmail does not "reply-all" by default :P Here is an answer from Wez to my reply: On 5/28/07, Pierre wrote: > I'm all for this solution. I asked to do it a couple of years ago (and > a couple of times since). All commits besides CS or docs (inline) > should have a bug report. It is then much easier to track the changes, > the discussions and, as you said here, be sure that all active > branches have it. To be effective, we'd need to require that all commits reference a bug report, otherwise one could forget to reference it and we'd "lose" the commit. We can create CS and Doc reports to allow those to be made without opening a report for each one. > What I would like to provide is a way to get the patches related to an > issue from our bug tracker. I'm not sure what's the best way to do it > but at least all related commits can be associated. A cron job can > fetch the commit mails and add them to the respective issues. Or can > we have a special mail sent to a php-bug-patches@php.net with the > complete patch and commit message? Yeah, I'd love that to work too. I think mailing into the bugs box would be the way to make it work. --Wez.