aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2004-11-29 23:06:51 +0000
committerNick Mathewson <nickm@torproject.org>2004-11-29 23:06:51 +0000
commitce505f5033794488df20670a4555e02da9ae81cb (patch)
tree0005a529e40d7240f79e31191ef13a1ae5ec3839
parent6507be4290a65c0ad7bbd614325e0b6f97c2446f (diff)
downloadtor-ce505f5033794488df20670a4555e02da9ae81cb.tar
tor-ce505f5033794488df20670a4555e02da9ae81cb.tar.gz
note possible alternative for how to do CVS versions; ask arma which he likes.
svn:r3023
-rw-r--r--src/or/or.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/or/or.h b/src/or/or.h
index 3f39f3d93..47eec972a 100644
--- a/src/or/or.h
+++ b/src/or/or.h
@@ -1647,6 +1647,11 @@ void clear_trusted_dir_servers(void);
* 0.1.1.7-cvs, 0.1.1.8-rc, 0.1.1.9-cvs. Eventually, we release 0.1.1.10.
* The stable CVS repository gets the version 0.1.1.11-maint_cvs; the
* next patch release is 0.1.1.12.
+ *
+ * XXXX(Alternatively, we could go: 0.1.1.1-alpha, 0.1.1.1-alpha_cvs,
+ * 0.1.1.2-alpha, 0.1.1.2-alpha_cvs . This wouldn't violate our
+ * only-one-release-per-number rule, since CVS versions aren't
+ * released. Roger?)
*/
typedef struct tor_version_t {
int major;