From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xen.org
Subject: untracked pvshim related dirty files in staging
Date: Wed, 28 Feb 2018 12:39:13 +0100 [thread overview]
Message-ID: <20180228113843.GA25447@aepfle.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 765 bytes --]
While building staging I got these two untracked dirty files.
I wonder what should be done about it?
Changes not staged for commit:
modified: tools/firmware/xen-dir/shim.config
Untracked files:
tools/firmware/xen-dir/xen-shim-syms
What is the value of adding version and branch name into the Xen
.config? I remember many years ago I submitted some change to Kbuild in
linux.git which prevents such jitter in .config. Perhaps it was just for
timestamps, I forgot.
--- a/tools/firmware/xen-dir/shim.config
+++ b/tools/firmware/xen-dir/shim.config
@@ -1,6 +1,6 @@
#
# Automatically generated file; DO NOT EDIT.
-# Xen/x86 4.11-unstable Configuration
+# Xen/x86 4.11-my_branch_name Configuration
#
CONFIG_X86_64=y
CONFIG_X86=y
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2018-02-28 11:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180228113843.GA25447@aepfle.de \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xen.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).