[source-date-epoch-spec] 01/01: Give "timestamp clamping" a bit more weight to acknowledge that we've been using it in practise
Ximin Luo
infinity0 at debian.org
Mon Oct 23 15:43:51 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 fafd6033a5d3fb670aa77c09ef63a6c40ac51dc2
Author: Ximin Luo <infinity0 at debian.org>
Date: Mon Oct 23 17:22:18 2017 +0200
Give "timestamp clamping" a bit more weight to acknowledge that we've been using it in practise
---
source-date-epoch-spec.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source-date-epoch-spec.xml b/source-date-epoch-spec.xml
index bdf2e79..b4faf0e 100644
--- a/source-date-epoch-spec.xml
+++ b/source-date-epoch-spec.xml
@@ -157,7 +157,7 @@
"current", but are nevertheless still specific to one
execution of the build process, they MUST use a
timestamp no later than the value of this variable.
- (This is sometimes called "timestamp clamping".)
+ This is often called "timestamp clamping".
</para>
<para>
Build processes MUST NOT unset this variable for child
--
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