From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] jffs2 whitespace
Date: Mon, 26 Sep 2005 12:53:59 +0400 [thread overview]
Message-ID: <4337B727.2050809@yandex.ru> (raw)
In-Reply-To: <20050925150635.GD28978@wohnheim.fh-wedel.de>
Jörn Engel wrote:
> I'm not sure about this. Apart from the binary operator cases, your
> changes are definitely a slight improvement. But the patch is also
> peeing on every lantern pole in the county:
> 61 files changed, 1677 insertions(+), 1713 deletions(-)
>
> How can I trust you that you didn't introduce a security problem on
> line 6789 of your 9485 line patch, by intention or not. I'd have to
> read it all, which is quite boring.
>
> And if all goes well, pretty much every single patch maintained
> outside of cvs would break after merging this. There must be a
> collision _somewhere_, after all.
>
> So I guess the short answer is "no".
>
> My usual approach to whitespace cleanup, btw., is as a first step
> before I change some code anyway. Even whitespace patches should get
> tested and since I need some testing anyway and they help me read and
> change the code, the cleanup is gaining me more than it costs.
Well, I looked through the patch and have not found anything really bad.
Some changes are neutral, but as for me the patch is OK. And why should
we care about external patches? Let people work them out and regenerate. :-)
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-09-26 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 0:05 [PATCH] jffs2 whitespace Peter Grayson
2005-09-25 15:06 ` Jörn Engel
2005-09-26 8:53 ` Artem B. Bityutskiy [this message]
2005-09-26 9:34 ` Jörn Engel
2005-09-26 9:46 ` Artem B. Bityutskiy
2005-09-26 11:01 ` Jörn Engel
2005-09-26 17:17 ` Peter Grayson
2005-09-26 17:21 ` Artem B. Bityutskiy
2005-09-26 17:28 ` Jörn Engel
2005-09-27 13:56 ` Artem B. Bityutskiy
2005-09-27 14:02 ` Jörn Engel
2005-09-27 20:58 ` Peter Grayson
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=4337B727.2050809@yandex.ru \
--to=dedekind@yandex.ru \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.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