diff options
| author | Nick Mathewson <nickm@torproject.org> | 2011-03-16 15:00:36 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2011-03-16 15:00:36 -0400 |
| commit | 6c6914c646c4ade95dd737788b30ffde871c9661 (patch) | |
| tree | 78ef88bd52f32081dc475357ac210e776cecb8aa /version-spec.txt | |
| parent | ab2e389479d5db84f9a7de5f0e2cf279934d19c6 (diff) | |
| download | torspec-6c6914c646c4ade95dd737788b30ffde871c9661.tar.gz torspec-6c6914c646c4ade95dd737788b30ffde871c9661.zip | |
Clarify what "alphabetical" and "lexical" mean to us.
Spotted by Robert Ransom
Diffstat (limited to 'version-spec.txt')
| -rw-r--r-- | version-spec.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/version-spec.txt b/version-spec.txt index 265717f..b017335 100644 --- a/version-spec.txt +++ b/version-spec.txt @@ -31,7 +31,7 @@ release. If the tag ends with "-cvs" or "-dev", you're looking at a development snapshot that came after a given release. If we *do* encounter two versions that differ only by status tag, we compare them - lexically. + lexically as ASCII byte strings. Now, we start each development branch with (say) 0.1.1.1-alpha. The patchlevel increments consistently as the status tag changes, for |