diff options
| author | Nick Mathewson <nickm@torproject.org> | 2016-05-30 16:18:16 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2016-05-30 16:18:16 -0400 |
| commit | 4f1a04ff9c74456c03ac67adb7ae780e4e77c71e (patch) | |
| tree | a7dde276330e86e166945af726d1e4d325f18a67 /src/or/onion.c | |
| parent | ce31db4326599c3f86307fca5286349150cb871e (diff) | |
| download | tor-4f1a04ff9c74456c03ac67adb7ae780e4e77c71e.tar.gz tor-4f1a04ff9c74456c03ac67adb7ae780e4e77c71e.zip | |
Replace nearly all XXX0vv comments with smarter ones
So, back long ago, XXX012 meant, "before Tor 0.1.2 is released, we
had better revisit this comment and fix it!"
But we have a huge pile of such comments accumulated for a large
number of released versions! Not cool.
So, here's what I tried to do:
* 0.2.9 and 0.2.8 are retained, since those are not yet released.
* XXX+ or XXX++ or XXX++++ or whatever means, "This one looks
quite important!"
* The others, after one-by-one examination, are downgraded to
plain old XXX. Which doesn't mean they aren't a problem -- just
that they cannot possibly be a release-blocking problem.
Diffstat (limited to 'src/or/onion.c')
| -rw-r--r-- | src/or/onion.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/or/onion.c b/src/or/onion.c index 4bed7ae226..944506e3af 100644 --- a/src/or/onion.c +++ b/src/or/onion.c @@ -51,7 +51,7 @@ static int ol_entries[MAX_ONION_HANDSHAKE_TYPE+1]; static int num_ntors_per_tap(void); static void onion_queue_entry_remove(onion_queue_t *victim); -/* XXXX024 Check lengths vs MAX_ONIONSKIN_{CHALLENGE,REPLY}_LEN. +/* XXXX Check lengths vs MAX_ONIONSKIN_{CHALLENGE,REPLY}_LEN. * * (By which I think I meant, "make sure that no * X_ONIONSKIN_CHALLENGE/REPLY_LEN is greater than |