warnings

[Adam Jackson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 02 September 2004 21:02, Jesse Barnes wrote:
> On Thursday, September 2, 2004 5:48 pm, Adam Jackson wrote:
> > As usual, the best way to do this would be to open a bug for it, attach
> > the patch, and await feedback.  Best to do it in stages too, for example
> > all of one class of warning for just the video drivers in one patch, to
> > make it easier to review.
>
> It's better to file a bug then post a patch to the list?  Won't more people
> see the patch if it goes to the list?  Ideally, a head janitor with checkin
> access could checkin such a patch after it had been approved by the list. 
> At least, that seems to work pretty well for lkml, but I'm biased.

I operate on the assumption that people regularly scan bugzilla for 
interesting new bugs, and only search through their email to find old 
discussions.  It's just too easy to lose a patch in email.  Also lkml lacks a 
corresponding authoritative bugzilla, so it may not be a fair comparison.

I don't really care much either way as long as good patches get merged, but I 
do get a warm fuzzy from seeing bug numbers in front of commit messages.  I 
suppose the mythical Xjanitor people will need to come up with a process and 
stick to it ;).

Seriously, who wants to act as patchmonkey for janitorial patches?  I'm 
willing to do it if no one else steps forward, but in a larger sense the 
janitation project needs a a set of goals and tasks, and I'm probably not the 
guy to come up with them.

- - ajax
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBN8VpW4otUKDs0NMRApmrAJ9XnS0gdRV826duQrn5wAhxSYtvGACfTBPN
XEAsj0bl61XK8E732tVHnBQ=
=J5dm
-----END PGP SIGNATURE-----