* untracked pvshim related dirty files in staging
@ 2018-02-28 11:39 Olaf Hering
0 siblings, 0 replies; only message in thread
From: Olaf Hering @ 2018-02-28 11:39 UTC (permalink / raw)
To: xen-devel
[-- 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-02-28 11:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-02-28 11:39 untracked pvshim related dirty files in staging Olaf Hering
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).