public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Junio C Hamano <junio@pobox.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	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>
Subject: Re: [PATCH] sched: leave sched_setscheduler earlier if possible.
Date: Sat, 26 Mar 2011 11:26:13 +0100	[thread overview]
Message-ID: <1301135173.2250.324.camel@laptop> (raw)
In-Reply-To: <7vzkoi4yl3.fsf@alter.siamese.dyndns.org>

On Fri, 2011-03-25 at 15:36 -0700, Junio C Hamano wrote:
> Peter Zijlstra <a.p.zijlstra@chello.nl> writes:
> 
> > 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:
> 
> Perhaps "git help attributes" and look for "funcname"?

Awesome so the diff.$foo.xfuncname is about what I want, except I seem
to need a .gitattributes file per repository. 

Is there a way to over-ride the default in a global way so that I can
only change ~/.gitconfig and not bother with all various repos I have?

Another question, the built-in patterns consist of multiple regexes, can
custom patterns also have multiple?


So what worked for me was:

~/.gitconfig:

[diff "cpp"]
	xfuncname = "^[[:alpha:]$_].*[^:]$"

and linux-2.6/.gitattributes:

*.h diff=cpp
*.c diff=cpp

What I tried was:

[diff]
  xfuncname = "^[[:alpha:]$_].*[^:]$"

But that didn't seem to work.. I also tried ~/.gitattributes, but again,
no joy.




  reply	other threads:[~2011-03-26 10:24 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
2011-03-25 22:36         ` Junio C Hamano
2011-03-26 10:26           ` Peter Zijlstra [this message]
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=1301135173.2250.324.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