From: Joe Perches <joe@perches.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org,
git <git@vger.kernel.org>
Subject: Re: [RFC/PATCH] Update coding standard to avoid ungrepable printk format strings
Date: Fri, 22 Feb 2008 08:58:30 -0800 [thread overview]
Message-ID: <1203699510.19319.56.camel@localhost> (raw)
In-Reply-To: <20080222132612.GA11717@basil.nowhere.org>
On Fri, 2008-02-22 at 14:26 +0100, Andi Kleen wrote:
> RFC: Update coding standard to avoid split up printk format strings
Perhaps it's more useful to have git become more content aware.
If git could track user specified file glob pattern ("*.[ch]$")
changes by statement terminator (";") and git could format
output by a user specified pass (lindent), many of the bike shed
paint discussions and a lot of commits would never occur.
parent reply other threads:[~2008-02-22 16:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20080222132612.GA11717@basil.nowhere.org>]
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=1203699510.19319.56.camel@localhost \
--to=joe@perches.com \
--cc=andi@firstfloor.org \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).