mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Urlichs <matthias@urlichs.de>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
	Nicolas Palix <npalix@diku.dk>,
	linux-kernel@vger.kernel.org,
	Yoann Padioleau <yoann.padioleau@gmail.com>,
	Julia Lawall <julia@diku.dk>,
	devel@driverdev.osuosl.org, Joe Perches <joe@perches.com>,
	Amerigo Wang <xiyou.wangcong@gmail.com>,
	akpm@linux-foundation.org
Subject: Re: [PATCH v2] scripts: add typdef removal tool
Date: Tue, 25 Aug 2009 14:35:52 +0000	[thread overview]
Message-ID: <1251210952.10339.1331.camel@kiste> (raw)
In-Reply-To: <4A918389.8050301@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 422 bytes --]

On Sun, 2009-08-23 at 19:59 +0200, Jiri Slaby wrote:
> -type f excludes directories.

Yes, but -o binds more loosely.

$ mkdir bar
$ find . -type f -name foo -o -name bar
bar
$

I like to pay attention to correct idioms. There is no problem in this
case because there are no directories named *.h in the kernel tree — but
people read code like that, and then apply it to situations where it
_does_ matter.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-08-25 14:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14  5:39 Luis R. Rodriguez
2009-08-17  6:02 ` Amerigo Wang
2009-08-21  8:48   ` Jiri Slaby
2009-08-23 13:09     ` Matthias Urlichs
2009-08-23 16:06       ` Américo Wang
2009-08-23 13:22   ` Matthias Urlichs
2009-08-23 16:04     ` Américo Wang
2009-08-23 17:59     ` Jiri Slaby
2009-08-25 14:35       ` Matthias Urlichs [this message]
2010-09-19  8:19 ` Pekka Enberg
2010-09-19  8:49   ` Joe Perches
2010-09-19  9:30     ` Pekka Enberg
2010-09-19 15:03       ` Luis R. Rodriguez

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=1251210952.10339.1331.camel@kiste \
    --to=matthias@urlichs.de \
    --cc=akpm@linux-foundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=jirislaby@gmail.com \
    --cc=joe@perches.com \
    --cc=julia@diku.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=npalix@diku.dk \
    --cc=xiyou.wangcong@gmail.com \
    --cc=yoann.padioleau@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

all inboxes | Powered by JetHome®