From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Oleksii Kurochko <oleksii.kurochko@gmail.com>
Subject: [PATCH] .gitignore: generalize *.new
Date: Tue, 28 Nov 2023 13:51:43 +0100 [thread overview]
Message-ID: <40438252-0d54-47f0-aad8-e76d57508bc5@suse.com> (raw)
It's not only in xen/include/xen/ that we generate (intermediate) *.new
files.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
---
Really I don't think I can spot what *.new we create in that specific
directory. xen/include/ certainly has some.
--- a/.gitignore
+++ b/.gitignore
@@ -17,6 +17,7 @@
*.so.[0-9]*
*.bin
*.bak
+*.new
*.tmp
*.spot
*.spit
@@ -277,7 +278,6 @@
xen/include/config/
xen/include/generated/
xen/include/public/public
-xen/include/xen/*.new
xen/include/xen/acm_policy.h
xen/include/xen/compile.h
xen/include/xen/hypercall-defs.h
next reply other threads:[~2023-11-28 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:51 Jan Beulich [this message]
2023-11-28 14:45 ` [PATCH] .gitignore: generalize *.new Oleksii
2023-11-29 18:00 ` Julien Grall
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=40438252-0d54-47f0-aad8-e76d57508bc5@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=julien@xen.org \
--cc=oleksii.kurochko@gmail.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.