[source-date-epoch-spec] 01/01: The issue stems from timestamps not being updated by git, not clamping

[Ximin Luo]

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 3785b49cf605789e1df7b2fe849b14015a178ab6
Author: Ximin Luo <infinity0 at debian.org>
Date:   Tue Nov 21 14:02:24 2017 +0100

    The issue stems from timestamps not being updated by git, not clamping
---
 source-date-epoch-spec.xml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/source-date-epoch-spec.xml b/source-date-epoch-spec.xml
index aa7b720..4718fd0 100644
--- a/source-date-epoch-spec.xml
+++ b/source-date-epoch-spec.xml
@@ -192,8 +192,9 @@
 		<para>
 			Developers could set <envar>SOURCE_DATE_EPOCH</envar> to the date
 			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.
+			it is recommended to also update all source file timestamps, which
+			git does not do by itself, otherwise old timestamps specific to the
+			developer's working tree may be embedded into the output.
 		</para>
 		<para>
 			Though it is not forbidden to set <envar>SOURCE_DATE_EPOCH</envar>

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/source-date-epoch-spec.git