[source-date-epoch-spec] 03/05: Document complexities about setting-from-git and clamping
Ximin Luo
infinity0 at debian.org
Mon Nov 13 16:12:32 UTC 2017
This is an automated email from the git hooks/post-receive script.
infinity0 pushed a commit to branch pu/1.1
in repository source-date-epoch-spec.
commit fb93f7ce5abd50832f8e0b927b6aa92ca8352794
Author: Ximin Luo <infinity0 at debian.org>
Date: Mon Nov 13 16:57:35 2017 +0100
Document complexities about setting-from-git and clamping
---
source-date-epoch-spec.xml | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/source-date-epoch-spec.xml b/source-date-epoch-spec.xml
index 8bd4e99..4ef5be1 100644
--- a/source-date-epoch-spec.xml
+++ b/source-date-epoch-spec.xml
@@ -186,12 +186,14 @@
<para>
Distributions could set <envar>SOURCE_DATE_EPOCH</envar> by using
the value of a changelog file. For instance, Debian packages can
- set it to the value of the last entry of
+ set it to the value of the latest entry of
<filename>debian/changelog</filename>.
</para>
<para>
Developers could set <envar>SOURCE_DATE_EPOCH</envar> to the date
- of the last commit in their version control system.
+ of the latest commit in their version control system. In this case,
+ it is recommended to also update source file timestamps to this
+ value, or else this may interact badly with any timestamp clamping.
</para>
</sect2>
<sect2>
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/source-date-epoch-spec.git
More information about the Reproducible-commits
mailing list