mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, dwmw2@infradead.org,
	torvalds@linux-foundation.org
Subject: Re: [path] don't diff generated firmware files
Date: Tue, 2 Sep 2008 03:14:19 +0400	[thread overview]
Message-ID: <20080901231419.GA5602@x200.localdomain> (raw)
In-Reply-To: <20080901150951.5cba4dc7@infradead.org>

On Mon, Sep 01, 2008 at 03:09:51PM -0700, Arjan van de Ven wrote:
> With the new firmware infrastructure in 2.6.27, some files are generated and shouldn't be
> diffed; add these 2 to the "dontdiff" file

> --- linux.trees.git/Documentation/dontdiff
> +++ linux.trees.git/Documentation/dontdiff
> @@ -5,6 +5,8 @@
>  *.css
>  *.dvi
>  *.eps
> +*.fw.gen.S
> +*.fw

Dontdiff is obsoleted because of .gitignore and should probably be auto-generated
from them.


  reply	other threads:[~2008-09-01 23:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 22:09 Arjan van de Ven
2008-09-01 23:14 ` Alexey Dobriyan [this message]
2008-09-12 17:17   ` Randy Dunlap
2008-09-12 17:17   ` [PATCH] dontdiff: more updates to be closer to gitignore Randy Dunlap
2008-09-12 17:18   ` [RFC/PATCH] dontdiff: generate from gitignore Randy Dunlap
2008-09-12 17:36     ` Linus Torvalds
2008-09-12 17:41       ` Randy Dunlap
2008-09-12 20:32         ` Kai Henningsen
     [not found] <e2e108260809130052u454b6920h9745c27eb2f4b20c@mail.gmail.com>
2008-09-14 18:23 ` [RFC PATCH] Script for generating Documentation/dontdiff from .gitignore files Eduard - Gabriel Munteanu
2008-09-15 15:34   ` Randy Dunlap
2008-09-16  3:26     ` [RFC PATCH] Script for generating Documentation/dontdiff from .gitignore files. (was Re: [RFC/PATCH] dontdiff: generate from gitignore) Eduard - Gabriel Munteanu

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=20080901231419.GA5602@x200.localdomain \
    --to=adobriyan@gmail.com \
    --cc=arjan@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®