RE: project status

[David Wagle <dwagle@frontiernet.net>]

I've asked about a dozen times to be removed from this list. I have 
followed the available instructions. EVery so often I get put back on it 
for some damn reason.

PLEASE GET ME THE FUCK OFF THIS THING NOW AND DON"T PUT ME BACK ON< EVER!
Thank you very much.



-----Original Message-----
From:	davej@suse.de [SMTP:davej@suse.de]
Sent:	Wednesday, January 10, 2001 1:34 PM
To:	Greg KH
Cc:	Arnaldo Carvalho de Melo; Burns, John; 'George Capehart'; 
'kernel-audit@mail.nl.linux.org'
Subject:	Re: project status

On Tue, 9 Jan 2001, Greg KH wrote:

> > 1. Someone checks out the TODO from CVS.
> > 2. Picks something, mentions to the list "I'm about to tackle item 38"
> >    (In case someone else already is working on it, in which case 
pointing
> >    them to the relevant person may be advisable.
> >    A project admin with CVS write access maybe marks it in the TODO
> >    file ?).
> > 3. After hacking fixups, the patch is sent here.
>
> And to the code's maintainer.  Please remember them :)

*nod*, of course. An oversight on my part.

> > 4. If the patch looks ok, its recommended to be sent to l-k/Linus/Alan.
> This should probably say:
>
> 4. If the maintainer agrees, then _they_ forward it on up the proper
>    chain of command.
>
> There is usually someone else in charge of the larger
> subsystem, that then will forward it to Linus in the end.  Let's not do
> an end run around the current kernel submission process.

Agreed. It may even be worth letting the maintainer know that item x
is being worked on by someone. It would be a pain if

a. The maintainer already had the fix in their private tree.
b. That item was due to become irrelevant due to code rewrite
c. Someone else already sent the maintainer that fix, but no-one else knew
   about it
d. The maintainer knows a better way to fix the problem than the
   proposed fix, but hadn't yet implemented it.

So yes, keeping the maintainer up to date with what's going on is also
an essential item.

regards,

Davej.

--
| Dave Jones.        http://www.suse.de/~davej
| SuSE Labs


Kernel-audit:  discussion list for security and the linux kernel
Archive:       http://mail.nl.linux.org/kernel-audit/


Kernel-audit:  discussion list for security and the linux kernel
Archive:       http://mail.nl.linux.org/kernel-audit/