summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2020-05-14put a . at the end of changes entrytor-0.4.3.5Roger Dingledine
2020-05-14unlist things that were already stable in 0.4.2.5Roger Dingledine
2020-05-14blurb for 0.4.3.5Nick Mathewson
2020-05-140.4.3.5 release notes: edit section headingsNick Mathewson
2020-05-140.4.3.5 ReleaseNotes: remove bugfixes on 0.4.3.Nick Mathewson
(These are not "changes since 0.4.2")
2020-05-14Start an 0.4.3.5 releasenotesNick Mathewson
This was made by taking all 0.4.3.x changelogs up to this point and sorting them.
2020-05-14remove 0.4.3.3-alpha from the release notes: alphas do not go there.Nick Mathewson
2020-05-140.4.3.5 changelog: collapse the sections.Nick Mathewson
2020-05-14Merge branch 'maint-0.4.3' into release-0.4.3Nick Mathewson
2020-05-14bump to 0.4.3.5Nick Mathewson
2020-05-14start changelog for 0.4.3.5Nick Mathewson
2020-05-14Merge branch 'maint-0.4.2' into maint-0.4.3Nick Mathewson
2020-05-14Merge branch 'maint-0.4.3' into release-0.4.3Nick Mathewson
2020-05-14Merge branch 'maint-0.4.1' into maint-0.4.2Nick Mathewson
2020-05-14Merge branch 'maint-0.3.5' into maint-0.4.1Nick Mathewson
2020-05-14Travis: temporarily fix stem version to d1174a83c2dcb7b8Nick Mathewson
This is a workaround for https://github.com/torproject/stem/issues/63
2020-05-06Merge branch 'maint-0.4.3' into release-0.4.3Nick Mathewson
2020-05-06Fix a boolean logic error when logging about invalid hostnames.Nick Mathewson
Fixes bug 34131; bugfix on 0.4.3.1-alpha.
2020-05-06connection_or_finished_flushing(): add a missing "break;"Nick Mathewson
This one is harmless like the others (so far)
2020-05-06Merge branch 'maint-0.4.2' into maint-0.4.3Nick Mathewson
2020-05-06Merge branch 'maint-0.4.1' into maint-0.4.2Nick Mathewson
2020-05-06btrack_orconn_cevent.c: Add a missing "break;"Nick Mathewson
2020-05-06Merge branch 'maint-0.4.3' into release-0.4.3Nick Mathewson
2020-05-06Merge branch 'maint-0.4.2' into maint-0.4.3Nick Mathewson
2020-05-06Merge branch 'maint-0.4.1' into maint-0.4.2Nick Mathewson
2020-05-06Merge branch 'maint-0.3.5' into maint-0.4.1Nick Mathewson
2020-05-06changes file for bug 34078.Nick Mathewson
2020-05-06Use __attribute__((fallthrough)) rather than magic GCC comments.Nick Mathewson
GCC added an implicit-fallthrough warning a while back, where it would complain if you had a nontrivial "case:" block that didn't end with break, return, or something like that. Clang recently added the same thing. GCC, however, would let you annotate a fall-through as intended by any of various magic "/* fall through */" comments. Clang, however, only seems to like "__attribute__((fallthrough))". Fortunately, GCC accepts that too. A previous commit in this branch defined a FALLTHROUGH macro to do the right thing if GNUC is defined; here we replace all of our "fall through" comments with uses of that macro. This is an automated commit, made with the following perl one-liner: #!/usr/bin/perl -i -p s#/\* *falls? ?thr.*?\*/#FALLTHROUGH;#i; (In order to avoid conflicts, I'm applying this script separately to each maint branch. This is the 0.4.3 version.)
2020-05-06Merge branch 'maint-0.4.2' into maint-0.4.3Nick Mathewson
This is an "ours" merge to avoid taking the maint-0.4.2 version of the 34078 fix.
2020-05-06Use __attribute__((fallthrough)) rather than magic GCC comments.Nick Mathewson
GCC added an implicit-fallthrough warning a while back, where it would complain if you had a nontrivial "case:" block that didn't end with break, return, or something like that. Clang recently added the same thing. GCC, however, would let you annotate a fall-through as intended by any of various magic "/* fall through */" comments. Clang, however, only seems to like "__attribute__((fallthrough))". Fortunately, GCC accepts that too. A previous commit in this branch defined a FALLTHROUGH macro to do the right thing if GNUC is defined; here we replace all of our "fall through" comments with uses of that macro. This is an automated commit, made with the following perl one-liner: #!/usr/bin/perl -i -p s#/\* *falls? ?thr.*?\*/#FALLTHROUGH;#i; (In order to avoid conflicts, I'm applying this script separately to each maint branch. This is the 0.4.2 version.)
2020-05-06Merge branch 'maint-0.4.1' into maint-0.4.2Nick Mathewson
This is an "ours" merge to avoid taking the 0.4.1 version of the 34078 fix.
2020-05-06Use __attribute__((fallthrough)) rather than magic GCC comments.Nick Mathewson
GCC added an implicit-fallthrough warning a while back, where it would complain if you had a nontrivial "case:" block that didn't end with break, return, or something like that. Clang recently added the same thing. GCC, however, would let you annotate a fall-through as intended by any of various magic "/* fall through */" comments. Clang, however, only seems to like "__attribute__((fallthrough))". Fortunately, GCC accepts that too. A previous commit in this branch defined a FALLTHROUGH macro to do the right thing if GNUC is defined; here we replace all of our "fall through" comments with uses of that macro. This is an automated commit, made with the following perl one-liner: #!/usr/bin/perl -i -p s#/\* *falls? ?thr.*?\*/#FALLTHROUGH;#i; (In order to avoid conflicts, I'm applying this script separately to each maint branch. This is the 0.4.1 version.)
2020-05-06Merge branch 'maint-0.3.5' into maint-0.4.1Nick Mathewson
This is an "ours" merge to avoid taking the 0.3.5 fix for 34078.
2020-05-06Use __attribute__((fallthrough)) rather than magic GCC comments.Nick Mathewson
GCC added an implicit-fallthrough warning a while back, where it would complain if you had a nontrivial "case:" block that didn't end with break, return, or something like that. Clang recently added the same thing. GCC, however, would let you annotate a fall-through as intended by any of various magic "/* fall through */" comments. Clang, however, only seems to like "__attribute__((fallthrough))". Fortunately, GCC accepts that too. A previous commit in this branch defined a FALLTHROUGH macro to do the right thing if GNUC is defined; here we replace all of our "fall through" comments with uses of that macro. This is an automated commit, made with the following perl one-liner: #!/usr/bin/perl -i -p s#/\* *falls? ?thr.*?\*/#FALLTHROUGH;#i;
2020-05-06Merge branch 'maint-0.4.3' into release-0.4.3Nick Mathewson
2020-05-06hs_dos.c: rewrite a comment not to say "fallthrough"Nick Mathewson
There's nothing wrong with the comment, but the script I'm about to apply wouldn't like it.
2020-05-06Merge branch 'maint-0.4.1' into maint-0.4.2Nick Mathewson
2020-05-06Merge branch 'maint-0.3.5' into maint-0.4.1Nick Mathewson
2020-05-06Merge branch 'maint-0.4.3' into release-0.4.3Nick Mathewson
2020-05-06Merge branch 'maint-0.4.2' into maint-0.4.3Nick Mathewson
2020-05-06Merge branch 'bug34078_prelim_041' into maint-0.4.1Nick Mathewson
2020-05-06Merge branch 'bug34078_prelim_035' into maint-0.3.5Nick Mathewson
2020-05-06Merge branch 'bug34078_prelim_035' into bug34078_prelim_041Nick Mathewson
2020-05-06Remove an incorrect "Fall through" comment.Nick Mathewson
2020-05-06address.c: add a single (harmless) missing break;Nick Mathewson
2020-05-06include compat_compiler for ed25519_donnaNick Mathewson
2020-05-06Replace some "fall through" comments not at the end of a case.Nick Mathewson
2020-05-06Replace a "fall through" comment that was outside a switch.Nick Mathewson
2020-05-06Add a fallthrough macro.Nick Mathewson
This macro defers to __attribute__((fallthrough)) on GCC (and clang). Previously we had been using GCC's magic /* fallthrough */ comments, but clang very sensibly doesn't accept those. Since not all compiler recognize it, we only define it when our configure script detects that it works. Part of a fix for 34078.
2020-05-04Merge branch 'maint-0.4.1' into maint-0.4.2Nick Mathewson