From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: tytso@mit.edu, randy.dunlap@oracle.com, arjan@infradead.org,
linux-kernel@vger.kernel.org, bcollins@ubuntu.com
Subject: Re: reviewing Ubuntu kernel patches
Date: Wed, 21 Jun 2006 13:25:12 -0700 [thread overview]
Message-ID: <20060621132512.12db84f6.akpm@osdl.org> (raw)
In-Reply-To: <20060621173841.GH9111@stusta.de>
On Wed, 21 Jun 2006 19:38:41 +0200
Adrian Bunk <bunk@stusta.de> wrote:
> When Andrew merges some small fix into an existing patch in -mm
> (e.g. "make a function static" or "fix a compile error"), he adds the
> Signed-off-by line of the small fix to the Signed-off-by lines of the
> patch.
>
> But the submitter of the fix does not necessarly have checked the
> legal or technical status of the rest of the patch.
>
> As an example, my only contribution to commit
> 6b3934ef52712ece50605dfc72e55d00c580831a was making signal_cachep
> static, and I do refuse any legal or technical responsibility for
> the rest of the patch (this shouldn't imply the rest of the patch was
> bad - it's simply not me who can is responsible for it).
Yes, nowadays I give the folded-in patch a mini-changelog, as in
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17/2.6.17-mm1/broken-out/slab-kmalloc-kzalloc-comments-cleanup-and-fix.patch
prev parent reply other threads:[~2006-06-21 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 23:22 reviewing Ubuntu kernel patches Randy Dunlap
2006-06-15 0:06 ` Ben Collins
2006-06-15 15:42 ` Arjan van de Ven
2006-06-16 5:39 ` Randy Dunlap
2006-06-16 14:03 ` Theodore Tso
2006-06-21 17:38 ` Adrian Bunk
2006-06-21 20:25 ` Andrew Morton [this message]
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=20060621132512.12db84f6.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bcollins@ubuntu.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=tytso@mit.edu \
/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