From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Cong Ding <dinggnu@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bin Wang <wbin00@gmail.com>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH RFC -next] Fix the trailing blank space issue
Date: Thu, 6 Dec 2012 19:54:48 +0000 [thread overview]
Message-ID: <20121206195448.1ff18422@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20121206163138.GC2510@gmail.com>
> I would suggest to write a series of scripts. And then announce a date
> (preferably some holiday like Xmas) to run these scripts. The announce is to
> avoid conflicts with other developers. It will save both developers' and
> subsystem maintains' time, do you agree?
And if any of them are wrong how will we notice ?
By all means generate them in subsystem sized chunks but they do need to
get a human glance just to be sure. If you send me drivers/tty for
example I'll go over it happily and give it an Ack unless something is
very odd.
And to be honest if they don't all get done - who cares. There are a
several thousand more serious things the scanning and analyser tools flag
that are much more useful to fix.
Alan
prev parent reply other threads:[~2012-12-06 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 9:08 [PATCH 1/1] sysfs: Fixed a trailing white space error Bin Wang
2012-12-06 15:42 ` [PATCH RFC -next] Fix the trailing blank space issue Cong Ding
2012-12-06 16:06 ` Greg Kroah-Hartman
2012-12-06 16:31 ` Cong Ding
2012-12-06 16:59 ` Greg Kroah-Hartman
2013-01-14 14:07 ` Bin Wang
2012-12-06 19:54 ` Alan Cox [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=20121206195448.1ff18422@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dinggnu@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wbin00@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).