From: Dan Carpenter <error27@gmail.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Use kstrdup rather than duplicating its implementation
Date: Tue, 02 Aug 2011 21:09:22 +0000 [thread overview]
Message-ID: <20110802210922.GC3839@shale.localdomain> (raw)
In-Reply-To: <1312313657.2629.20.camel@localhost.localdomain>
On Tue, Aug 02, 2011 at 09:34:14PM +0200, Thomas Meyer wrote:
> Does somebody maybe have a script for doing this split of an mbox file?
> maybe this script could also call get_maintainer.pl and change the To:
> field accordingly?
>
> Just asking...
Checking it by hand builds character. :) Reviewers have to check
each patch by hand for mistakes and malice so this serves as a small
test to see if it's worth bothering maintainers about it.
regards,
dan carpenter
next prev parent reply other threads:[~2011-08-02 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 16:21 [PATCH] Use kstrdup rather than duplicating its implementation Thomas Meyer
2011-08-02 18:05 ` Dan Carpenter
2011-08-02 19:34 ` Thomas Meyer
2011-08-02 21:09 ` Dan Carpenter [this message]
2011-08-03 7:06 ` walter harms
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=20110802210922.GC3839@shale.localdomain \
--to=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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