1. 22 Apr, 2022 1 commit
  2. 15 Mar, 2022 1 commit
    • Abseil Team's avatar
      Running clang-format over all of GoogleTest · b007c54f
      Abseil Team authored
      A few tests are examining code locations and looking af the resulting line
      numbers to verify that GoogleTest shows those to users correctly. Some of those
      locations change when clang-format is run. For those locations, I've wrapped
      portions in:
      // clang-format off
      ...
      // clang-format on
      
      There may be other locations that are currently not tickled by running
      clang-format.
      
      PiperOrigin-RevId: 434844712
      Change-Id: I3a9f0a6f39eff741c576b6de389bef9b1d11139d
      b007c54f
  3. 03 Dec, 2018 1 commit
    • Abseil Team's avatar
      Googletest export · 26743363
      Abseil Team authored
      Applied fixes for ClangTidy modernize-use-override and modernize-use-using.
      
      PiperOrigin-RevId: 223800219
      26743363
  4. 14 Aug, 2018 1 commit
    • Gennadiy Civil's avatar
      · a3c0dd0f
      Gennadiy Civil authored
      Comments changes, no functionality changes
      a3c0dd0f
  5. 15 May, 2017 1 commit
    • Nico Weber's avatar
      Use std::string and ::string explicitly in gtest and gmock code. · 09fd5b3e
      Nico Weber authored
      This merges a Google-internal change (117235625).
      
      Original CL description:
      This CL was created manually in about an hour with sed, a Python script
      to find all the places unqualified 'string' was mentioned, and some help
      from Emacs to add the "std::" qualifications, plus a few manual tweaks.
      09fd5b3e
  6. 25 Aug, 2015 1 commit
  7. 10 Apr, 2012 1 commit
  8. 20 May, 2011 1 commit
  9. 14 Sep, 2010 1 commit
  10. 10 Dec, 2008 1 commit