All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@firmix.at>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] de-initialization of = 0 globals
Date: Tue, 13 Dec 2005 15:35:37 +0000	[thread overview]
Message-ID: <1134488137.30759.31.camel@tara.firmix.at> (raw)
In-Reply-To: <63769.192.96.150.57.1134482519.squirrel@mail.interexcel.co.za>

[-- Attachment #1: Type: text/plain, Size: 2179 bytes --]

On Tue, 2005-12-13 at 17:16 +0200, Jaco Kroon wrote:
> Bernd Petrovitsch wrote:
> > On Tue, 2005-12-13 at 16:01 +0200, Jaco Kroon wrote:
> > [...]
> > 
> >>Also, if I'm going to be sending patches for these it's obviously a patch
> >>per affected file, so if I'm going to be sending let's say a hundred of
> >>these patches it's still a mail per patch or do I just archive them
> >>somehow and attach them or do I place them on a webserver and mail a uri
> >>to them?
> > 
> > 
> > Make one patch per subsystem (unless told otherwise from core LKML
> > personnel directly) since
> > -) these are trivial patches and
> > -) you actually want to mail them to the relevant
> >    maintainer/mailing-list and Cc: LKML/k-j only.
> > 
> > 	Bernd
> 
> Ah bugger. That makes it quite a bit more complex :(.  It's relatively

Yes. But otherwise it is IMHO more "complex" (or cumbersome) for the
readers (and their will be more than only 1) getting e.g. 100 mails with
trivial fixes for 100 files or flooding some linux-<subsystem>@ ML with
12 Emails fixin such trivial stuff in 12 different files.

> easy to single out all the cases (and fix them), but automating the
> grouping of files into subsystems and assigning maintainers to those
> subsystems isn't as trivial.

I thought about proposing a new field to maintainers where the relevant
subdirectories/files listed so that one knows whom to bug if I changed a
list of given files.
But this is quite a work, ongoing since this changes and I don't know
how people react.

The simpler start is probably to generate one large patch for the Kernel
and separate patches for larger subsystems (IDE, SCSI, etc.) out of it
since you can just work with an editor.
And near the end you can send the last ones in one patch and see what
happens (in the best of all worlds, the patch is accept for -mm which
usually creates directly enough pressure so that subsystem maintainers
take it from there).

Or you just send the one large patch and see what happens.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


[-- Attachment #2: Type: text/plain, Size: 168 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2005-12-13 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13 14:01 [KJ] de-initialization of = 0 globals Jaco Kroon
2005-12-13 14:19 ` Bernd Petrovitsch
2005-12-13 15:16 ` Jaco Kroon
2005-12-13 15:35 ` Bernd Petrovitsch [this message]
2005-12-13 20:41 ` Jesper Juhl
2005-12-13 21:01 ` Jaco Kroon
2005-12-13 21:43 ` Jesper Juhl
2005-12-13 21:59 ` Jesper Juhl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1134488137.30759.31.camel@tara.firmix.at \
    --to=bernd@firmix.at \
    --cc=kernel-janitors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.