[Reproducible-commits] [source-date-epoch-spec] 01/01: - fix some formatting and tweak some wording to be more consistent

Ximin Luo infinity0 at debian.org
Thu Aug 27 15:23:28 UTC 2015


This is an automated email from the git hooks/post-receive script.

infinity0 pushed a commit to branch master
in repository source-date-epoch-spec.

commit 928bd1c531c1035b847ee774a1e07cf8b440863f
Author: Ximin Luo <infinity0 at debian.org>
Date:   Thu Aug 27 17:23:05 2015 +0200

    - fix some formatting and tweak some wording to be more consistent
---
 source-date-epoch-spec.xml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/source-date-epoch-spec.xml b/source-date-epoch-spec.xml
index a9487ba..bb41737 100644
--- a/source-date-epoch-spec.xml
+++ b/source-date-epoch-spec.xml
@@ -223,9 +223,9 @@
 			for child processes to consume, for example by reading
 			the time of the latest VCS commit or filesystem entry if
 			there are uncommitted changes. However, they MUST NOT do
-			this if the variable is already set (e.g. by a parent
-			process such as a distribution-specific build scripts, or
-			by the user themselves).
+			this if the variable is already set, for example by a
+			parent process such as distribution build scripts, or by
+			the user themselves.
 		</para>
 		<warning>
 			<para>
@@ -241,18 +241,18 @@
 		<para>
 			If the value is missing or empty, the upstream build
 			process chooses its own behaviour; this situation is
-			undistinguishable from one that is not following this
+			indistinguishable from one that is not following this
 			specification. However, we RECOMMEND that the behaviour
 			should more closely approximate the date of the last
 			modification to the source code. This may be detected
 			automatically if the source is on a developer's machine
-			or from source control, or hard-coded into an official
-			release tarball; falling back to the "current" date and
-			time of the build is NOT RECOMMENDED.
+			or from VCS, or hard-coded into an official release
+			tarball; falling back to the "current" date and time of
+			the build is NOT RECOMMENDED.
 		</para>
 		<para>
 			If the value is malformed, the upstream build process
-			should exit with a non-zero error code.
+			SHOULD exit with a non-zero error code.
 		</para>
 	</sect2>
 </sect1>

-- 
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