From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 5/5] hvmloader: add knob for fixed VGABIOS date string
Date: Wed, 25 Mar 2015 09:46:22 +0100 [thread overview]
Message-ID: <20150325084622.GA11487@aepfle.de> (raw)
In-Reply-To: <1427212640.21742.453.camel@citrix.com>
On Tue, Mar 24, Ian Campbell wrote:
> Is it expected that they should all be settable independently? Or would
> one global setting be sufficient?
A single timestamp would be nice, sure.
> If so then a single variable which can be set to something accepted by
> date -d which could be formatted in each location would seem preferable.
I did consider that. But that adds a dependency on 'date -d'. Not sure
if every build environment supports that. On Linux everyone will most
likely run date(1) from coreutils, which understands -d. Not sure about
BSD. I dont have access to BSD right now to check if their date
understands it. Their online manuals state that -d means something
else...
http://netbsd.gw.com/cgi-bin/man-cgi?date++NetBSD-current
http://www.freebsd.org/cgi/man.cgi?query=date
http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/date.1?query=date
In the end I think its acceptable to have a number of variables from
environment or make cmdline. Its only used during automated package
build.
Olaf
next prev parent reply other threads:[~2015-03-25 8:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 17:24 [PATCH 0/5] tools: various changes Olaf Hering
2015-03-20 17:24 ` [PATCH 1/5] tools/mkrpm: improve version.release handling Olaf Hering
2015-03-23 16:15 ` George Dunlap
2015-03-23 17:05 ` Olaf Hering
2015-03-23 17:52 ` Olaf Hering
2015-03-23 18:07 ` George Dunlap
2015-03-23 18:49 ` Olaf Hering
2015-03-23 19:00 ` George Dunlap
2015-03-24 12:15 ` Olaf Hering
2015-03-20 17:24 ` [PATCH 2/5] tools/hotplug: introduce XENSTORED_ARGS= in sysconfig file Olaf Hering
2015-03-24 15:53 ` Ian Campbell
2015-03-20 17:24 ` [PATCH 3/5] INSTALL: mention variables for reproducible builds Olaf Hering
2015-03-24 15:55 ` Ian Campbell
2015-03-25 8:49 ` Olaf Hering
2015-03-25 10:55 ` Ian Campbell
2015-03-20 17:24 ` [PATCH 4/5] hvmloader: add knob for fixed SMBIOS date string Olaf Hering
2015-03-23 8:36 ` Jan Beulich
2015-03-23 9:15 ` Olaf Hering
2015-03-23 12:24 ` Jan Beulich
2015-03-23 12:25 ` Jan Beulich
2015-03-20 17:24 ` [PATCH 5/5] hvmloader: add knob for fixed VGABIOS " Olaf Hering
2015-03-24 15:57 ` Ian Campbell
2015-03-25 8:46 ` Olaf Hering [this message]
2015-03-25 10:55 ` Ian Campbell
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=20150325084622.GA11487@aepfle.de \
--to=olaf@aepfle.de \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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 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.