Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44985
Return-Path: <pierre.php@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 17685 invoked from network); 16 Jul 2009 07:48:10 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 16 Jul 2009 07:48:10 -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 72.14.220.157 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: 72.14.220.157 fg-out-1718.google.com  
Received: from [72.14.220.157] ([72.14.220.157:7127] helo=fg-out-1718.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 44/5D-47962-83BDE5A4 for <internals@lists.php.net>; Thu, 16 Jul 2009 03:48:09 -0400
Received: by fg-out-1718.google.com with SMTP id 13so1033103fge.0
        for <internals@lists.php.net>; Thu, 16 Jul 2009 00:48:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        bh=zAse/ZhRkPq5flGkQu0iwsCV7BF4sBoRREmZBEHKi1E=;
        b=bjE4V/YzGPwxOk7wm5MhcvrkqhgokfYhxQWVEfNJ3KvGSvpItzKQIWtnDP+EDoj4gq
         Hh051RjH01fwComDNon7GLZ8mKdnzpckF6oNJXAiTmgfFf1OY6LnbnqTJa+XiDoNqXFl
         RVBpnHQlWwhib4E2dbzUSS/UC8zWYSFsYiiuM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=K0LpuvkNkVMRFxz3TU4WFG78rVFTWFbQWlWx8shuKT4QBDeyvATroz6PVlgdkZldnh
         BgWXRJ0MtOGkgiJejzB1uaDWRp6Avhgi28jYxk1pFstIF36Qg5pb3ft92Nzn/j+DMNkA
         78ETIcRLyQyLh7CHTmRZpMEBn2D/WJYP3vEiA=
MIME-Version: 1.0
Received: by 10.86.59.2 with SMTP id h2mr5849225fga.60.1247730485762; Thu, 16 
	Jul 2009 00:48:05 -0700 (PDT)
In-Reply-To: <3AEF93D9-A92A-4CAA-9754-603423BA3B29@roshambo.org>
References: <FBE08A97-79DF-4311-8DE4-2237DEAEFC59@roshambo.org>
	 <4A5E137E.3010905@Sun.COM> <4A5E245E.7080402@sci.fi>
	 <3AEF93D9-A92A-4CAA-9754-603423BA3B29@roshambo.org>
Date: Thu, 16 Jul 2009 09:48:05 +0200
Message-ID: <fe05d1540907160048u2f8b91eatc348fdfc5a0bfcc9@mail.gmail.com>
To: Philip Olson <philip@roshambo.org>
Cc: jani.taskinen@iki.fi, Sriram Natarajan <Sriram.Natarajan@sun.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] bug tracker planning
From: pierre.php@gmail.com (Pierre Joye)

On Thu, Jul 16, 2009 at 5:54 AM, Philip Olson<philip@roshambo.org> wrote:

> As for 'capturing related bugs', I imagine the [optional] tagging would help
> with that... or do you have something specific in mind?

Related bugs are more a list of bugs # related to a given one, or
being a dependency, a coma separated list of # should do it (one to n
relation in the db).


Cheers,
-- 
Pierre

http://blog.thepimp.net | http://www.libgd.org