From: Pete Zaitcev <zaitcev@redhat.com>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk loglevel cleanup (again)
Date: Tue, 27 Nov 2001 12:58:48 -0500 [thread overview]
Message-ID: <200111271758.fARHwmO22631@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1006876204.12313.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.1006876204.12313.linux-kernel2news@redhat.com>
Linus refused wholesale cleanups in the past. Try to identify
worst offenders and start from those, and work through component
maintainers. It's a lot more work, but you have to tough it out.
-- Pete
> When I was making this patch I couldn't resist and fixed
> messed up tabs around affected printks, wrapped some
> lines longer than 80 columns, fixed some typos.
next parent reply other threads:[~2001-11-27 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1006876204.12313.linux-kernel2news@redhat.com>
2001-11-27 17:58 ` Pete Zaitcev [this message]
2001-11-28 16:01 ` [PATCH] printk loglevel cleanup (again) vda
2001-11-28 15:39 ` Small security bug with misconfigured access rights Giuliano Pochini
2001-11-28 18:03 ` Jordan Russell
2001-11-27 19:43 [PATCH] printk loglevel cleanup (again) vda
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=200111271758.fARHwmO22631@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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