[tor-commits] [torspec/master] version-spec: allow EXTRA_INFO to appear multiple times.

[nickm@xxxxxxxxxxxxxx]

commit b50917d9c33d448947296472cc83e9f6ff1e98c9
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date:   Wed Sep 20 09:55:42 2017 -0400

    version-spec: allow EXTRA_INFO to appear multiple times.
---
 version-spec.txt | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/version-spec.txt b/version-spec.txt
index 4a3dccf..1f25cd1 100644
--- a/version-spec.txt
+++ b/version-spec.txt
@@ -21,7 +21,7 @@
 2. The New Way
 
  After 0.1.0, versions are of the format:
-    MAJOR.MINOR.MICRO[.PATCHLEVEL][-STATUS_TAG][ (EXTRA_INFO)]
+    MAJOR.MINOR.MICRO[.PATCHLEVEL][-STATUS_TAG][ (EXTRA_INFO)]*
  The stuff in parentheses is optional.  As before, MAJOR, MINOR, MICRO,
  and PATCHLEVEL are numbers, with an absent number equivalent to 0.
  All versions should be distinguishable purely by those four
@@ -38,7 +38,8 @@
  The EXTRA_INFO is also purely informational, often containing information
  about the SCM commit this version came from. It is surrounded by parentheses
  and can't contain whitespace. Unlike the STATUS_TAG this never impacts the way
- that versions should be compared.
+ that versions should be compared. EXTRA_INFO may appear any number of
+ times. Tools should generally not parse EXTRA_INFO entries.
 
  Now, we start each development branch with (say) 0.1.1.1-alpha.  The
  patchlevel increments consistently as the status tag changes, for



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits