From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Q] Sending a large patch
Date: Wed, 14 May 2014 10:47:32 +0000 [thread overview]
Message-ID: <1400064452.18277.19.camel@thorin> (raw)
In-Reply-To: <CAAvxhqBUO2HSgZjw=H7=Bd2gdw=JSjAs2Lx8E7rrGw8uqieZAg@mail.gmail.com>
On Mit, 2014-05-14 at 01:48 +0100, Masaru Nomura wrote:
[...]
> 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
And you are really sure that is more readable afterwards with the
additional line breaks?
> correct the bugs and send one commit. But I think it's a pain for
> reviewers to check all of them within one patch.
Apart from the questionable usefulness of the above, you should split it
per subsystem/maintainer so that people do not need to look for "their"
parts.
Additionally, the maintainer may take the patch (and you are done) or
reject it (and you are also done;-).
Bernd
--
Bernd Petrovitsch Email : bernd@petrovitsch.priv.at
LUGA : http://www.luga.at
next prev parent reply other threads:[~2014-05-14 10:47 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
2014-05-14 10:47 ` Bernd Petrovitsch [this message]
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=1400064452.18277.19.camel@thorin \
--to=bernd@petrovitsch.priv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox