xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Maximilian Engelhardt <maxi@daemonizer.de>
To: xen-devel@lists.xenproject.org
Cc: Maximilian Engelhardt <maxi@daemonizer.de>,
	Ian Jackson <iwj@xenproject.org>, Wei Liu <wl@xen.org>,
	Jan Beulich <jbeulich@suse.com>
Subject: [RESEND] [XEN PATCH v1 0/1] Use reproducible date in docs
Date: Sat, 13 Feb 2021 15:48:24 +0100	[thread overview]
Message-ID: <cover.1613227389.git.maxi@daemonizer.de> (raw)

This is a resend of my v1 patch from [1] which has not been accepted
yet.

The -d "@..." syntax was introduced in GNU date about 2005, so I assume
a version supporting this syntax is available, if SOURCE_DATE_EPOCH is
defined. If SOURCE_DATE_EPOCH is not defined nothing changes with
respect to the current behavior.

In response to my first submission Jan Beulich mentioned in [2] it would
be good to probe for the availability of the -d "@..." syntax of GNU
date, as Jan couldn't find it when looking at an older documentation of
GNU date. I later found out and reported in [3] that while the syntax
has been implemented in GNU date in about 2005, the documentation has
only been updated in 2011.

I also submitted a v2 version that implemented the suggested probing of
the capabilities of the "date" command in [4]. However Wei Liu responded
a shorter version of the patch would be preferred, so I'm resending v1
now.

I'm fine with v1 or v2, both fix the issue of generating reproducible
documentation. This patch is the last upstream patch needed for get xen
built reproducibly in the next Debian release.

If both patches are not seen as appropriate, please tell me what changes
I should implement.

Thanks,
Maxi

[1] https://lists.xenproject.org/archives/html/xen-devel/2020-12/msg01518.html
[2] https://lists.xenproject.org/archives/html/xen-devel/2020-12/msg01564.html
[3] https://lists.xenproject.org/archives/html/xen-devel/2020-12/msg01698.html
[4] https://lists.xenproject.org/archives/html/xen-devel/2020-12/msg01715.html
[5] https://lists.xenproject.org/archives/html/xen-devel/2021-01/msg00178.html

Maximilian Engelhardt (1):
  docs: set date to SOURCE_DATE_EPOCH if available

 docs/Makefile | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

-- 
2.20.1



             reply	other threads:[~2021-02-13 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-13 14:48 Maximilian Engelhardt [this message]
2021-02-13 14:48 ` [XEN PATCH v1 1/1] docs: set date to SOURCE_DATE_EPOCH if available Maximilian Engelhardt

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=cover.1613227389.git.maxi@daemonizer.de \
    --to=maxi@daemonizer.de \
    --cc=iwj@xenproject.org \
    --cc=jbeulich@suse.com \
    --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 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).