[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] untracked pvshim related dirty files in staging


  • To: xen-devel@xxxxxxxxxxxxx
  • From: Olaf Hering <olaf@xxxxxxxxx>
  • Date: Wed, 28 Feb 2018 12:39:13 +0100
  • Delivery-date: Wed, 28 Feb 2018 11:39:28 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

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: signature.asc
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.