Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
For the correct definition of lexical order, search for "lexical
comparison". It's what your favorite language does for string
comparison, unless your favorite language is something really
esoteric.
In short:
If A and B are equal at every position, they are lexically equal.
Otherwise, if A is a prefix of B, A precedes B.
Otherwise, let i be the first position where A differs from
B. If A[i] precedes B[i], A precedes B.
|
|
Tor versions often contain information about the SCM commit they came from, for
instance...
0.2.3.16-alpha-dev (git-8be6058d8f31e578)
This isn't part of the spec, which in turn choked stem when I tried to parse
those versions. Adding this in and better defining a couple other points...
- The STATUS_TAG should only contain non-whitespace. Otherwise... well, just
about *anything* could be a 'valid' status tag.
- The spec says that status tags should be "compared lexically". The ASCII
value of 'Z' is greater than 'A' so I guess this means that they're sorted in
a reverse alphabetical order. This seems weird, but clarifying it.
|
|
Spotted by Robert Ransom
|
|
Tor doesn't use SVN anymore, making $Revision$, $Id$ and $Date$
meaningless. Remove them without replacement.
|
|
svn:r17407
|
|
svn:r16369
|
|
Re-number misnumbered spec sections. No more having to refer to "the first of two section 6.1s."
svn:r9683
|
|
clarify recent spec stuff
svn:r8808
|
|
svn:r8804
|
|
svn:r5941
|
|
svn:r3783
|