From: rklein@nvidia.com (rklein at nvidia.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: update gitignore file
Date: Thu, 10 Feb 2011 17:26:56 -0800 [thread overview]
Message-ID: <1297387616-29390-1-git-send-email-rklein@nvidia.com> (raw)
From: Rhyland Klein <rklein@nvidia.com>
Updating the .gitignore file to ignore 3 files that are always created in
manual builds to cleanup git status results.
Signed-off-by: Rhyland Klein <rklein@nvidia.com>
---
arch/arm/boot/compressed/.gitignore | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/compressed/.gitignore b/arch/arm/boot/compressed/.gitignore
index ab204db..c52a6dd 100644
--- a/arch/arm/boot/compressed/.gitignore
+++ b/arch/arm/boot/compressed/.gitignore
@@ -1,3 +1,6 @@
font.c
piggy.gz
vmlinux.lds
+lib1funcs.S
+piggy.gzip
+vmlinux
--
1.7.0.4
next reply other threads:[~2011-02-11 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 1:26 rklein at nvidia.com [this message]
2011-02-11 14:15 ` [PATCH] arm: update gitignore file Sergei Shtylyov
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=1297387616-29390-1-git-send-email-rklein@nvidia.com \
--to=rklein@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).