From: Bart Van Assche <bart.vanassche@gmail.com>
To: Jesper Juhl <trivial@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.25.1] Suppress more generated files via Documentation/dontdiff
Date: Fri, 2 May 2008 17:16:02 +0200 [thread overview]
Message-ID: <200805021716.02753.bart.vanassche@gmail.com> (raw)
Can the patch below please be reviewed ? Last time I ran diff over two kernel
trees I noted that several generated files were included in the diff. The
patch below suppresses these generated files (modules.order, timeconst.h and
several vdso* and vdso32* files).
Signed-off-by: bart.vanassche@gmail.com
--- orig/linux-2.6.25.1/Documentation/dontdiff 2008-05-01 23:45:25.000000000
+0200
+++ linux-2.6.25.1/Documentation/dontdiff 2008-05-02 15:43:51.000000000
+0200
@@ -142,6 +142,7 @@ mkprep
mktables
mktree
modpost
+modules.order
modversions.h*
offset.h
offsets.h
@@ -173,10 +174,11 @@ split-include
tags
tftpboot.img
times.h*
+timeconst.h
tkparse
trix_boot.h
utsrelease.h*
-vdso.lds
+vdso*[^Sch]
version.h*
vmlinux
vmlinux-*
next reply other threads:[~2008-05-02 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 15:16 Bart Van Assche [this message]
2008-05-20 7:16 ` [PATCH 2.6.25.1] Suppress more generated files via Documentation/dontdiff Bart Van Assche
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=200805021716.02753.bart.vanassche@gmail.com \
--to=bart.vanassche@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.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