Skip to content

C
Chromium_Depot_tools
Switch branch/tag
  1. 19 Nov, 2013 2 commits
    • 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
    • pgervais@chromium.org's avatar
      Fixed URL to "using git" instructions · d6617f3f
      pgervais@chromium.org authored 
      BUG=

Review URL: https://codereview.chromium.org/65933005

git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@235857 0039d316-1c4b-4281-b951-d872f2087c98
      d6617f3f
  3. 18 Nov, 2013 1 commit
  5. 17 Nov, 2013 1 commit
  7. 15 Nov, 2013 2 commits
  9. 14 Nov, 2013 3 commits
  11. 13 Nov, 2013 1 commit
  13. 11 Nov, 2013 1 commit
  15. 08 Nov, 2013 1 commit
  17. 07 Nov, 2013 2 commits
  19. 06 Nov, 2013 1 commit
    • deymo@chromium.org's avatar
      my_activity: Port gerrit to the new gerrit_util API. · f8be2769
      deymo@chromium.org authored 
      This patch adds a new function QueryAllChanges to gerrit_util.py
allowing the caller to iterate the list of changes regardless the
maximum limit of changes per request that the server supports (by
default 500 according to gerrit's documentation).

my_activity.py is ported to use this function instead of urllib2 to
manually make the request. This also adds support for authentication
since gerrit_util.py already supports it, and the internal gerrit
instance is now re-enabled.

Finally, two minor bugs are fixed on the hanlding of returned
results: The DETAILED_ACCOUNTS option is passed to gerrit to request
the email addresses of the referenced users and users without an
email address, such as the "Gerrit Code Review" user on the internal
gerrit, are now supported.

BUG=chromium:311649,chromium:281695
TEST=Manual run "my_activity.py -u USER" for some users.

Review URL: https://codereview.chromium.org/50283002

git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@233166 0039d316-1c4b-4281-b951-d872f2087c98
      f8be2769
  21. 05 Nov, 2013 1 commit
  23. 04 Nov, 2013 1 commit
  25. 01 Nov, 2013 1 commit
  27. 31 Oct, 2013 3 commits
  29. 30 Oct, 2013 1 commit
  31. 28 Oct, 2013 1 commit
  33. 25 Oct, 2013 2 commits
  35. 23 Oct, 2013 1 commit
  37. 22 Oct, 2013 1 commit
  39. 17 Oct, 2013 4 commits
  41. 16 Oct, 2013 4 commits
  43. 15 Oct, 2013 2 commits
  45. 14 Oct, 2013 1 commit
  47. 11 Oct, 2013 1 commit
  49. 10 Oct, 2013 1 commit