From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: lkml <linux-kernel@vger.kernel.org>, Michael Prokop <mika@grml.org>
Subject: Re: [PATCH] Documentation/dontdiff: large update
Date: Mon, 18 Apr 2011 18:22:57 -0700 [thread overview]
Message-ID: <1303176177.31723.58.camel@Joe-Laptop> (raw)
In-Reply-To: <20110418160809.f10c0b62.rdunlap@xenotime.net>
On Mon, 2011-04-18 at 16:08 -0700, Randy Dunlap wrote:
> Update to Documentation/dontdiff, based on many updates to
> various .gitignore patches over the last 2 years.
[]
> --- lnx-2639-r3g8-dontdiff.orig/Documentation/dontdiff
> +++ lnx-2639-r3g8-dontdiff/Documentation/dontdiff
[]
> -int16.c
> -int1.c
> -int2.c
> -int32.c
> -int4.c
> -int8.c
> +int*.c
Is this really a good idea?
$ find -name "int*.c" | wc -l
115
next prev parent reply other threads:[~2011-04-19 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 23:08 [PATCH] Documentation/dontdiff: large update Randy Dunlap
2011-04-19 1:22 ` Joe Perches [this message]
2011-04-19 4:46 ` Randy Dunlap
2011-04-20 16:14 ` [PATCH v2] " Randy Dunlap
2011-04-19 2:40 ` [PATCH] " Paul Mundt
2011-04-19 4:47 ` Randy Dunlap
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=1303176177.31723.58.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika@grml.org \
--cc=rdunlap@xenotime.net \
/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