1. 20 Mar, 2014 1 commit
    • revwalk: don't try to find merge bases when there can be none · 704b55cc
      As a way to speed up the cases where we need to hide some commits, we
      find out what the merge bases are so we know to stop marking commits as
      uninteresting and avoid walking down a potentially very large amount of
      commits which we will never see. There are however two oversights in
      current code.
      
      The merge-base finding algorithm fails to recognize that if it is only
      given one commit, there can be no merge base. It instead walks down the
      whole ancestor chain needlessly. Make it return an empty list
      immediately in this situation.
      
      The revwalk does not know whether the user has asked to hide any commits
      at all. In situation where the user pushes multiple commits but doesn't
      hide any, the above fix wouldn't do the trick. Keep track of whether the
      user wants to hide any commits and only run the merge-base finding
      algorithm when it's needed.
      Carlos Martín Nieto committed
  2. 19 Mar, 2014 5 commits
  3. 18 Mar, 2014 6 commits
  4. 17 Mar, 2014 5 commits
  5. 13 Mar, 2014 1 commit
  6. 12 Mar, 2014 2 commits
  7. 10 Mar, 2014 5 commits
  8. 07 Mar, 2014 14 commits
  9. 06 Mar, 2014 1 commit