From: Theodore Ts'o <tytso@mit.edu>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/5] fs: ext4: balloc: Fixing code style issues
Date: Tue, 05 May 2015 02:31:15 +0000 [thread overview]
Message-ID: <20150505023115.GA16076@thunk.org> (raw)
In-Reply-To: <1430786599-3843-1-git-send-email-adirkuhn@gmail.com>
On Tue, May 05, 2015 at 12:43:14AM +0000, Adir Kuhn wrote:
> Fixing code style issues
NACK. I only take code style changes if we are making changes in the
surrounding code. Code style changes break pending patches that other
developers might be sending me and so not only do they add zero value,
they are actively harmful.
- Ted
prev parent reply other threads:[~2015-05-05 2:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 0:43 [PATCH 0/5] fs: ext4: balloc: Fixing code style issues Adir Kuhn
2015-05-05 2:31 ` Theodore Ts'o [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=20150505023115.GA16076@thunk.org \
--to=tytso@mit.edu \
--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