From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kcalloc: Re-order the first two out-of-order args to kcalloc().
Date: Sat, 09 Dec 2006 22:55:56 +0100 [thread overview]
Message-ID: <457B30EC.8020805@s5r6.in-berlin.de> (raw)
In-Reply-To: <84144f020612090618g27ac861ka4ad693a0dee1928@mail.gmail.com>
Pekka Enberg wrote:
> On 12/9/06, Robert P. J. Day <rpjday@mindspring.com> wrote:
>> normally what i would do but, in the case of that patch, there are
>> five files affected, *all* of which are in totally different
>> subsystems (macintosh, net, scsi, usb, sunrpc). are you suggesting
>> that up to 5 different people be CC'ed?
>>
>> and what about source-wide aesthetic changes that might touch dozens
>> or hundreds of files?
>
> Well, it depends. There are no fixed rules in the art of patch
> feeding. FWIW, I probably would send this patch just to akpm too.
Yes, patches like this one are no big deal. But being involved in subsystem
maintenance, I find patches split up per subsystem much easier to handle.
Ccing the subsystem maintainers doen't make much sens if you don't split the
patch for them to integrate separately.
--
Stefan Richter
-=====-=-==- ==-- -=--=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2006-12-09 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 23:41 Robert P. J. Day
2006-12-09 13:53 ` Pekka Enberg
2006-12-09 13:54 ` Pekka Enberg
2006-12-09 14:03 ` Robert P. J. Day
2006-12-09 14:18 ` Pekka Enberg
2006-12-09 21:55 ` Stefan Richter [this message]
2006-12-09 14:00 ` Robert P. J. Day
2006-12-09 14:13 ` Pekka Enberg
2006-12-09 14:17 ` Robert P. J. Day
2006-12-09 14:31 ` Pekka Enberg
2006-12-09 14:35 ` Robert P. J. Day
2006-12-09 21:57 ` Stefan Richter
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=457B30EC.8020805@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rpjday@mindspring.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®