[source-date-epoch-spec] 02/03: try to move an example to the example section, and expand it as well

[Mattia Rizzolo]

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

mattia pushed a commit to branch pu/editorial_crap
in repository source-date-epoch-spec.

commit a99a3f005dcaf1e3be0f1939238f14d7a034cf42
Author: Mattia Rizzolo <mattia at debian.org>
Date:   Sat Nov 4 14:08:42 2017 +0100

    try to move an example to the example section, and expand it as well
    
    Signed-off-by: Mattia Rizzolo <mattia at debian.org>
---
 source-date-epoch-spec.xml | 17 ++++++++++++++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/source-date-epoch-spec.xml b/source-date-epoch-spec.xml
index 625e42c..bf5a971 100644
--- a/source-date-epoch-spec.xml
+++ b/source-date-epoch-spec.xml
@@ -144,9 +144,7 @@
 			different executions of the build, depending only on the
 			source code. It SHOULD be set to the last modification
 			time of the source, incorporating any packaging-specific
-			modifications. For example, in Debian, the timestamp
-			of the latest entry in
-			<filename>debian/changelog</filename>.
+			modifications.
 		</para>
 		<para>
 			Build processes MUST use this variable for embedded
@@ -179,6 +177,19 @@
 <sect1>
 	<title>Examples</title>
 	<sect2>
+		<title>Setting the variable</title>
+		<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
+			<filename>debian/changelog</filename>.
+		</para>
+		<para>
+			Developers could set <envar>SOURCE_DATE_EPOCH</envar> to the date
+			of the last commit in theri version control system.
+		</para>
+	</sect2>
+	<sect2>
 		<title>Timestamp clamping</title>
 		<para>
 			One can reasonably assume that all source timestamps are

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