An error occurred fetching the project authors.
  1. 18 May, 2016 4 commits
  2. 17 May, 2016 1 commit
  3. 16 May, 2016 7 commits
  4. 15 May, 2016 2 commits
  5. 13 May, 2016 3 commits
  6. 12 May, 2016 13 commits
  7. 11 May, 2016 3 commits
    • Yorick Peterse's avatar
      Updated 8.7.4 CHANGELOG entries · c446a865
      Yorick Peterse authored
      [ci skip]
      c446a865
    • Sean McGivern's avatar
      Group commits by date in server timezone · d9574a7b
      Sean McGivern authored
      `Time#to_date` just takes the (timezone-less) year, date, and month, and
      creates a new date from that. Because the commits in the list are
      grouped by date, rather than chunked when the date changes, a commit can
      be shown in the wrong order if its CommitDate has a timezone-less date
      that's different to other commits around it.
      
      Convert all CommitDates to the server timezone before grouping, as that
      will at least produce consistent results. Users can still see a
      timestamp on the commit that doesn't match the date it's grouped under,
      because the timestamp shown uses the user's local timezone, and the
      grouping uses the server's timezone, but that was an issue anyway.
      d9574a7b
    • Sean McGivern's avatar
      Only generate repository push email once · 5f27e26b
      Sean McGivern authored
      The repository push email can be very expensive to generate, especially
      with syntax-highlighted diffs. Instead of generating the email for each
      recipient, generate one email object and reset the Message-Id and To
      headers for each recipient. (Cloning would also be expensive in the case
      of large emails, although probably not as bad as generating from
      scratch.)
      5f27e26b
  8. 10 May, 2016 7 commits