From: Brian Gerst <bgerst@didntduck.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH] gitignore shared objects
Date: Thu, 05 Jan 2006 12:10:52 -0500 [thread overview]
Message-ID: <43BD531C.3060801@didntduck.org> (raw)
Many arches make shared objects for VDSOs. Generally exclude them.
Signed-off-by: Brian Gerst <bgerst@didntduck.org>
---
commit 78a3333da041f4ec40d2fda241b7a491a69c44b7
tree 648d14cc3e86dc286b8fc9f9ffa99f213fc4e23d
parent d5b9ab9d83c4beda74115d03b9bb9bad843f9d55
author Brian Gerst <bgerst@didntduck.org> Thu, 05 Jan 2006 11:08:25 -0500
committer Brian Gerst <bgerst@didntduck.org> Thu, 05 Jan 2006 11:08:25 -0500
.gitignore | 1 +
arch/x86_64/ia32/.gitignore | 1 -
2 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/.gitignore b/.gitignore
index a4b576e..3f8fb68 100644
--- a/.gitignore
+++ b/.gitignore
@@ -10,6 +10,7 @@
*.a
*.s
*.ko
+*.so
*.mod.c
#
diff --git a/arch/x86_64/ia32/.gitignore b/arch/x86_64/ia32/.gitignore
deleted file mode 100644
index 48ab174..0000000
--- a/arch/x86_64/ia32/.gitignore
+++ /dev/null
@@ -1 +0,0 @@
-vsyscall*.so
next reply other threads:[~2006-01-05 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 17:10 Brian Gerst [this message]
2006-01-06 19:53 ` [PATCH] gitignore shared objects Sam Ravnborg
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=43BD531C.3060801@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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