1. 12 Mar, 2019 1 commit
  2. 11 Mar, 2019 7 commits
  3. 08 Mar, 2019 3 commits
  4. 07 Mar, 2019 4 commits
  5. 06 Mar, 2019 4 commits
  6. 05 Mar, 2019 5 commits
  7. 04 Mar, 2019 5 commits
  8. 03 Mar, 2019 1 commit
  9. 02 Mar, 2019 2 commits
  10. 01 Mar, 2019 2 commits
  11. 28 Feb, 2019 2 commits
  12. 27 Feb, 2019 1 commit
  13. 26 Feb, 2019 2 commits
  14. 25 Feb, 2019 1 commit
    • Bruce Dawson's avatar
      Check for impossible date ranges · 2afcf22a
      Bruce Dawson authored
      If you specify the wrong year to the -b flag then you may end up with an
      inverted time range that is entirely in the future, and this causes odd
      failures. Or at least that's what I've heard. This detects some of these
      error cases and halts.
      
      Also a one-line git cl format cleanup.
      
      Change-Id: Iede80faed00d4857443b3a1d853fa2ba69f47023
      Reviewed-on: https://chromium-review.googlesource.com/c/1487744
      Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
      Auto-Submit: Bruce Dawson <brucedawson@chromium.org>
      Reviewed-by: 's avatarDirk Pranke <dpranke@chromium.org>
      2afcf22a