From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Q] Sending a large patch
Date: Wed, 14 May 2014 07:35:42 +0000 [thread overview]
Message-ID: <20140514073542.GA22735@mwanda> (raw)
In-Reply-To: <CAAvxhqBUO2HSgZjw=H7=Bd2gdw=JSjAs2Lx8E7rrGw8uqieZAg@mail.gmail.com>
On Wed, May 14, 2014 at 01:48:48AM +0100, Masaru Nomura wrote:
> Hi,
>
> Can anyone help me with “how to properly deal with a large patch” please?
>
> Now, I'm cleaning up a file and it has over 100 warnings of line over
> 80 character issues. As the problem seems to be the same, I may
> correct the bugs and send one commit. But I think it's a pain for
> reviewers to check all of them within one patch.
>
> What do you think I could do?
100 is not bad. Is this is all in one driver? I say go ahead and send
it.
regards,
dan carpenter
next prev parent reply other threads:[~2014-05-14 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 0:48 [Q] Sending a large patch Masaru Nomura
2014-05-14 7:35 ` Dan Carpenter [this message]
2014-05-14 10:47 ` Bernd Petrovitsch
2014-05-14 14:07 ` Masaru Nomura
2014-05-14 14:14 ` Dan Carpenter
2014-05-14 14:16 ` Masaru Nomura
2014-05-14 14:28 ` Bernd Petrovitsch
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=20140514073542.GA22735@mwanda \
--to=dan.carpenter@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox