1. 11 Jun, 2015 1 commit
    • commit: ignore multiple author fields · 65d69fe8
      Some tools create multiple author fields. git is rather lax when parsing
      them, although fsck does complain about them. This means that they exist
      in the wild.
      
      As it's not too taxing to check for them, and there shouldn't be a
      noticeable slowdown when dealing with correct commits, add logic to skip
      over these extra fields when parsing the commit.
      Carlos Martín Nieto committed
  2. 10 Jun, 2015 7 commits
  3. 09 Jun, 2015 2 commits
  4. 08 Jun, 2015 1 commit
  5. 07 Jun, 2015 1 commit
  6. 06 Jun, 2015 1 commit
  7. 02 Jun, 2015 3 commits
  8. 31 May, 2015 1 commit
  9. 29 May, 2015 3 commits
    • git__tolower: a tolower() that isn't dumb · 75a4636f
      Some brain damaged tolower() implementations appear to want to
      take the locale into account, and this may require taking some
      insanely aggressive lock on the locale and slowing down what should
      be the most trivial of trivial calls for people who just want to
      downcase ASCII.
      Edward Thomson committed
    • git__strcasecmp: treat input bytes as unsigned · 006548da
      Treat input bytes as unsigned before doing arithmetic on them,
      lest we look at some non-ASCII byte (like a UTF-8 character) as a
      negative value and perform the comparison incorrectly.
      Edward Thomson committed
    • Rename GIT_EMERGECONFLICT to GIT_ECONFLICT · 885b94aa
      We do not error on "merge conflicts"; on the contrary, merge conflicts
      are a normal part of merging.  We only error on "checkout conflicts",
      where a change exists in the index or the working directory that would
      otherwise be overwritten by performing the checkout.
      
      This *may* happen during merge (after the production of the new index
      that we're going to checkout) but it could happen during any checkout.
      Edward Thomson committed
  10. 28 May, 2015 15 commits
  11. 27 May, 2015 4 commits
  12. 26 May, 2015 1 commit