Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29854
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain seanius.net from 66.93.22.232 cause and error)
To: internals@lists.php.net
Date: Tue, 29 May 2007 00:59:39 +0200
User-Agent: KMail/1.9.7
Cc: "Wez Furlong" <kingwez@gmail.com>,
 "Ilia Alshanetsky" <ilia@prohost.org>,
 "Edin Kadribasic" <edin@krug.dk>
References: <4e89b4260705280856t47429e54ofcc182e02a6627e5@mail.gmail.com>
In-Reply-To: <4e89b4260705280856t47429e54ofcc182e02a6627e5@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart1225534.17O0WFrGO2";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-ID: <200705290059.42761.seanius@seanius.net>
Subject: Re: [PHP-DEV] better changeset tracking
From: seanius@seanius.net (sean finney)

--nextPart1225534.17O0WFrGO2
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

hi folks,

On Monday 28 May 2007 17:56:54 Wez Furlong wrote:
> I think we could do with investing a little bit of time into finding a
> way to automatically review commits to see if they have been merged to
> all relevant branches.   For this to be viable, we should probably
> adopt the practice of explicitly referencing a bug number in all
> commits (could be enforced by the commit hook); we can then analyze
> the commit messages to make sure that commits referencing a particular
> bug number have a corresponding set of commits in the branches, and
> vice versa.

this would be of immense, immense help to 3rd party distributors of php, su=
ch=20
as debian (and redhat, and others, i'm sure).   currently it's a rather=20
trying experience to go digging through commit histories for something that=
=20
was fixed "in the latest cvs snapshot" at some point in time.  i think i=20
posted a feature request along these lines at some time in the past... :)


	sean

--nextPart1225534.17O0WFrGO2
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBGW17eynjLPm522B0RApeyAJ9Xd4bCdRW0AGOP6gTDHQRSrLwluACfXFwN
fw8S4V2gXHkgx6L9jNlPh30=
=eX3V
-----END PGP SIGNATURE-----

--nextPart1225534.17O0WFrGO2--