1. 09 Feb, 2018 1 commit
    • Torne (Richard Coles)'s avatar
      Don't fetch tags when using --no-history. · 08ca04b2
      Torne (Richard Coles) authored
      After the initial gclient sync, "fetch --no-history" was adding a
      fetchspec to the config for the main repository that causes all tags to
      be downloaded in future. This means that after fetching a repository
      with no history, the very next git pull (or other remote update
      operation) will download all the tags, including all the history
      referred to by those tags, leaving you with an almost-complete checkout
      of the top-level repository that takes up much more space.
      
      Fix this by skipping the "git config" command that requests the tags
      when using no-history.
      
      Change-Id: Ia31baa6a90df014ebc1e8c2ed6e05de3ad27d415
      Reviewed-on: https://chromium-review.googlesource.com/909653Reviewed-by: 's avatarAaron Gable <agable@chromium.org>
      Commit-Queue: Richard Coles <torne@chromium.org>
      08ca04b2
  2. 29 Jan, 2018 1 commit
  3. 29 Nov, 2017 1 commit
  4. 12 Jul, 2017 1 commit
    • Dan Jacques's avatar
      [git] Remove hard-coded "depot_tools" Git. · 209a681f
      Dan Jacques authored
      Several tools, including the "git" recipe module, hard-code a
      checkout-relative "git.bat" path. Git is a feature that is provided by
      the system, both to tooling and recipes:
      
      1) For users, "depot_tools" must be on PATH, and during setup it will
         have installed "git.bat", ensuring that Git tooling is available in
         PATH.
      2) For bots, the system is responsible for providing "git.bat" on PATH.
         This is typically done at "/b/depot_tools/git.bat", which is sync'd
         through the "update_scripts" step.
      
      By formally treating Git as a system resource, we absolve Windows bots
      and users from manually installing a depot_tools-local Git, bringing
      them in line with other platforms.
      
      BUG=chromium:590806
      TEST=local
      
      Change-Id: I93e89855cdd330a2ba7a8cfb8117a1789d1ab54e
      Reviewed-on: https://chromium-review.googlesource.com/568694
      Commit-Queue: Daniel Jacques <dnj@chromium.org>
      Reviewed-by: 's avatarRobbie Iannucci <iannucci@chromium.org>
      209a681f
  5. 16 Dec, 2016 1 commit
  6. 26 Sep, 2016 1 commit
  7. 22 Sep, 2016 1 commit
  8. 09 May, 2016 1 commit
  9. 04 Dec, 2015 1 commit
  10. 19 Sep, 2015 1 commit
  11. 17 Jun, 2015 1 commit
  12. 15 Jun, 2015 2 commits
  13. 10 Jun, 2015 1 commit
  14. 26 Feb, 2015 1 commit
  15. 25 Nov, 2014 1 commit
  16. 22 Oct, 2014 1 commit
  17. 06 Aug, 2014 2 commits
  18. 05 Aug, 2014 2 commits
  19. 06 May, 2014 1 commit
  20. 03 Apr, 2014 1 commit
  21. 18 Mar, 2014 1 commit
  22. 20 Feb, 2014 1 commit
  23. 12 Feb, 2014 1 commit
  24. 13 Dec, 2013 1 commit
    • digit@chromium.org's avatar
      fetch.py: Add '--nohooks' option. · 3596d585
      digit@chromium.org authored
      'fetch chromium' will fail if the build dependencies are not already installed
      on the host machine, because it runs 'gclient sync' which, by default, will run
      hooks that will try to run build/gyp_chromium (which will then fail).
      
      This introduces a --nohooks option that solve the problem by allowing the
      user to do the following:
      
        1) fetch --nohooks <recipe>
        2) src/build/install-build-deps.sh
        3) fetch <recipe>
      
      BUG=325795
      TEST=Run 'fetch --nohooks chromium' in a temporary 'clean' chroot directory.
      R=maruel@chromium.org,jochen@chromium.org,scottmg@chromium.org,agable@chromium.org
      
      Review URL: https://codereview.chromium.org/106403003
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@240680 0039d316-1c4b-4281-b951-d872f2087c98
      3596d585
  25. 18 Apr, 2013 1 commit
  26. 12 Apr, 2013 2 commits
  27. 11 Apr, 2013 1 commit
  28. 04 Apr, 2013 2 commits
  29. 03 Apr, 2013 7 commits