1. 30 Oct, 2015 1 commit
  2. 28 Oct, 2015 2 commits
  3. 09 Oct, 2014 1 commit
  4. 28 Jul, 2014 1 commit
  5. 02 Jun, 2014 1 commit
  6. 13 Mar, 2014 1 commit
  7. 11 Mar, 2014 1 commit
  8. 24 Feb, 2014 1 commit
  9. 19 Nov, 2013 1 commit
    • iannucci@chromium.org's avatar
      Add git-number script to calculate generation numbers for commits. · aa74cf65
      iannucci@chromium.org authored
      Compatible with any git topology (multiple roots, weird branching/merging, etc.)
      I can't get it to be any faster (in python). Suggestions welcome :).
      
      On z600/linux, this takes 5.1s to calculate the initial count for 2e3de954ef0a
      (HEAD on src.git at the time of writing). Subsequent lookups take ~0.06s. For
      reference, this machine takes 3s to just list the revisions in sorted order
      without any additional processing (using rev-list).
      
      All calculations are stored in a git-notes-style ref with the exception that the
      leaf 'tree' object which would normally be stored in a git-notes world is
      replaced with a packed binary file which consists of records [hash int]. Each
      run of this script will create only 1 commit object on this internal ref which
      will have as its parents:
        * The previous git number commit
        * All of the target commits we calculated numbers for.
      This ref is then excluded on subsequent invocations of rev-list, which means that
      git-number will only ever process commit objects which it hasn't already
      calculated a value for. It also prevents you from attempting to number this
      special ref :).
      
      This implementation only has a 1-byte fanout which seems to be the best
      performance for the repos we're dealing with (i.e. on the order of 500k commit
      objects).  Bumping this up to a 2-byte fanout became extremely slow (I suspect
      the internal caching structures I'm using are not efficient in this mode and
      could be improved). Using no fanout is slower than the 1 byte fanout for lookups
      by about 30%.
      
      R=agable@chromium.org, stip@chromium.org, szager@chromium.org
      BUG=280154,309692,skia:1639
      
      Review URL: https://codereview.chromium.org/26109002
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@236035 0039d316-1c4b-4281-b951-d872f2087c98
      aa74cf65
  10. 01 Nov, 2013 1 commit
  11. 31 Oct, 2013 2 commits
  12. 30 Oct, 2013 1 commit
  13. 06 Nov, 2012 3 commits
  14. 14 Feb, 2012 1 commit
  15. 28 Sep, 2011 1 commit
  16. 01 Jun, 2011 1 commit
    • cmp@chromium.org's avatar
      Make git-cl and update_depot_tools msys-compatible. · 4c6e404c
      cmp@chromium.org authored
      This change makes it possible to run 'git cl' from
      a Command Prompt using only the auto-installed git
      from depot_tools.  It is needed because in MSysGit,
      'git cl' invokes 'git' which calls 'git-cl'.  While
      'git-cl' is pulled from depot_tools (since it's in
      PATH), depot_tools/python_bin is not in PATH, and
      so we execute git_cl.py through our auto-installed
      python.exe directly.
      
      update_depot_tools is fixed so that if we find
      the auto-installed svn and git in depot_tools, we
      execute those directly, otherwise falling back to
      calling them based on PATH.
      
      In both git-cl and update_depot_tools, we only enable
      this new behavior if uname in PATH reports a 'MINGW'
      environment.  This should not trigger on any other
      environment where uname exists, including Cygwin which
      should report 'CYGWIN'.
      Review URL: http://codereview.chromium.org/7020035
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@87510 0039d316-1c4b-4281-b951-d872f2087c98
      4c6e404c
  17. 25 May, 2011 1 commit
  18. 24 May, 2011 1 commit
  19. 29 Mar, 2011 1 commit
  20. 23 Dec, 2010 1 commit
  21. 18 Oct, 2010 3 commits
  22. 06 Oct, 2010 1 commit
  23. 13 Jul, 2010 1 commit
  24. 17 Feb, 2010 1 commit
  25. 16 Feb, 2010 1 commit
  26. 18 Nov, 2009 1 commit
  27. 04 Aug, 2009 1 commit
  28. 09 Jun, 2009 1 commit
  29. 05 Jun, 2009 1 commit
  30. 11 May, 2009 1 commit
  31. 23 Apr, 2009 1 commit