It could be done, but it would take a bit of a change in the way we do
things.  When fixing something you would always need to go to the bug
database and find the related bugs and put those bug ids in the commit
message.  And most fixes end up being a combination of commits so any
particular bug is likely to have links to a number of cvs commits.  I am
not sure this will be all that useful as the patches will often not be
standalone things that can be applied to the current released code.

-Rasmus

On Fri, 23 Aug 2002, Marko Karppinen wrote:

>  Dan and Sebastian:
>  >> it would be rather cool if a bug is fixed in CVS, the patch would be
>  >> attached to the bug in bugs.php.net. Would
>  >
>  > It would be cool, but it'd also be impractical.  Much of the time
>  > stuff in
>  > CVS HEAD is different than that in a release (witness the streams
>  > introduction now).
> 
>  I think the good thing about this change would be that it would allow
>  people to follow PHP development from the bug system. Currently it
>  is an all-or-nothing proposition; either you follow php-dev and php-cvs
>  and are "in touch" with things, or you don't and aren't.
> 
>  The way to implement this would be adding it to the commit script
>  at cvs.php.net; a keyword in the commit message would attach the
>  patch to the bug, similarly to the NEWS and ChangeLog magic
>  that is already happening.
> 
>  Coupled with people filing feature requests for the non-bugs they are
>  working on, this would go a long way into enabling people to follow
>  only the specific areas of PHP development they are interested in.
> 
>  mk
> 
> 
>  --
>  PHP Development Mailing List <http://www.php.net/>
>  To unsubscribe, visit: http://www.php.net/unsub.php
> 


-- 
PHP Quality Assurance Mailing List <http://www.php.net/> 
To unsubscribe, visit: http://www.php.net/unsub.php