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 <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] 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.

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to