public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Dario Faggioli <raistlin@linux.it>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>,
	Gregory Haskins <ghaskins@novell.com>,
	Mike Galbraith <efault@gmx.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Junio C Hamano <junio@pobox.com>
Subject: Re: [PATCH] sched: leave sched_setscheduler earlier if possible.
Date: Fri, 25 Mar 2011 14:07:10 +0100	[thread overview]
Message-ID: <1301058430.2250.211.camel@laptop> (raw)
In-Reply-To: <1301057573.14261.168.camel@gandalf.stny.rr.com>

On Fri, 2011-03-25 at 08:52 -0400, Steven Rostedt wrote:
> > And you know I prefer to fix the tools ;-)
> 
> And when the tools are fixed, I'll also prefer
> 
So instead of complaining about it, tell people to use:

QUILT_DIFF_OPTS="-F ^[[:alpha:]\$_].*[^:]\$"

Just like you tell them about all your other patch style issues.

Junio, know of any way to make git-diff do the same? The purpose is to
skip labels as functions so that people stop doing stupid crap like
indenting labels, eg.:

void foo(void)
{
 again:
	/* do stuff */
	if (retry)
		goto again;
}

instead of the normal:

void foo(void)
{
again:
	/* do stuff */
	if (retry)
		goto again;
}


  reply	other threads:[~2011-03-25 13:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 13:00 [PATCH] sched: leave sched_setscheduler earlier if possible Dario Faggioli
2011-03-24 14:21 ` Steven Rostedt
2011-03-25 10:28   ` Peter Zijlstra
2011-03-25 12:52     ` Steven Rostedt
2011-03-25 13:07       ` Peter Zijlstra [this message]
2011-03-25 22:36         ` Junio C Hamano
2011-03-26 10:26           ` Peter Zijlstra
2011-03-26 10:30             ` Peter Zijlstra
2011-03-31 12:39 ` [tip:sched/urgent] sched: Leave sched_setscheduler() earlier if possible, do not disturb SCHED_FIFO tasks tip-bot for Dario Faggioli

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=1301058430.2250.211.camel@laptop \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@osdl.org \
    --cc=efault@gmx.de \
    --cc=ghaskins@novell.com \
    --cc=junio@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=raistlin@linux.it \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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