From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: [Qemu-trivial] [PATCH for-4.0] maint: Ignore built elf2dmp
Date: Wed, 13 Mar 2019 09:45:57 -0500 [thread overview]
Message-ID: <20190313144557.8845-1-eblake@redhat.com> (raw)
Commit 3fa2d384 added a binary 'elf2dmp' but did not ignore it
during an in-tree build.
Signed-off-by: Eric Blake <eblake@redhat.com>
---
Yes, I know we want to get rid of in-tree builds for 4.1; but
for 4.0, this patch may still make sense.
.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitignore b/.gitignore
index 77522561b8e..42d2d473559 100644
--- a/.gitignore
+++ b/.gitignore
@@ -6,6 +6,7 @@
/config-target.*
/config.status
/config-temp
+/elf2dmp
/trace-events-all
/trace/generated-events.h
/trace/generated-events.c
--
2.20.1
next reply other threads:[~2019-03-13 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 14:45 Eric Blake [this message]
2019-03-14 9:21 ` [Qemu-trivial] [Qemu-devel] [PATCH for-4.0] maint: Ignore built elf2dmp Stefano Garzarella
2019-03-14 15:00 ` [Qemu-trivial] " Laurent Vivier
2019-03-14 21:22 ` [Qemu-trivial] [Qemu-devel] " Philippe Mathieu-Daudé
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=20190313144557.8845-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).