1. 03 Mar, 2020 1 commit
  2. 28 Feb, 2020 2 commits
  3. 27 Feb, 2020 5 commits
  4. 24 Feb, 2020 4 commits
  5. 21 Feb, 2020 2 commits
  6. 20 Feb, 2020 2 commits
  7. 18 Feb, 2020 1 commit
  8. 17 Feb, 2020 1 commit
  9. 16 Feb, 2020 1 commit
  10. 14 Feb, 2020 2 commits
  11. 13 Feb, 2020 3 commits
    • Evan Hunt's avatar
      apply the modified style · e851ed0b
      Evan Hunt authored
      e851ed0b
    • Ondřej Surý's avatar
      Use clang-tidy to add curly braces around one-line statements · 056e133c
      Ondřej Surý authored
      The command used to reformat the files in this commit was:
      
      ./util/run-clang-tidy \
      	-clang-tidy-binary clang-tidy-11
      	-clang-apply-replacements-binary clang-apply-replacements-11 \
      	-checks=-*,readability-braces-around-statements \
      	-j 9 \
      	-fix \
      	-format \
      	-style=file \
      	-quiet
      clang-format -i --style=format $(git ls-files '*.c' '*.h')
      uncrustify -c .uncrustify.cfg --replace --no-backup $(git ls-files '*.c' '*.h')
      clang-format -i --style=format $(git ls-files '*.c' '*.h')
      056e133c
    • Ondřej Surý's avatar
      Use coccinelle to add braces to nested single line statement · 36c6105e
      Ondřej Surý authored
      Both clang-tidy and uncrustify chokes on statement like this:
      
      for (...)
      	if (...)
      		break;
      
      This commit uses a very simple semantic patch (below) to add braces around such
      statements.
      
      Semantic patch used:
      
      @@
      statement S;
      expression E;
      @@
      
      while (...)
      - if (E) S
      + { if (E) { S } }
      
      @@
      statement S;
      expression E;
      @@
      
      for (...;...;...)
      - if (E) S
      + { if (E) { S } }
      
      @@
      statement S;
      expression E;
      @@
      
      if (...)
      - if (E) S
      + { if (E) { S } }
      36c6105e
  12. 12 Feb, 2020 3 commits
  13. 10 Feb, 2020 2 commits
  14. 08 Feb, 2020 1 commit
    • Michał Kępień's avatar
      Fix the "pipelined" system test on OpenBSD · a5e90f2a
      Michał Kępień authored
      On OpenBSD, the bin/tests/system/pipelined/ans5/ans.py script does not
      shut down when it is sent the SIGTERM signal.  What seems to be
      happening is that starting the UDP listening thread somehow makes the
      accept() calls in the script's main thread uninterruptible and thus the
      SIGTERM signal sent to the main thread does not get processed until a
      TCP connection is established with the script's TCP socket.  Work around
      the issue by setting a timeout for operations performed on the script's
      TCP socket, so that each accept() call in the main thread's infinite
      loop returns after at most 1 second, allowing termination signals sent
      to the script to be processed.
      a5e90f2a
  15. 07 Feb, 2020 10 commits