commit | 2ff302929ca12b309ab35a3f957cd0179f382d74 | [log] [tgz] |
---|---|---|
author | Gabe Black <gabeblack@chromium.org> | Thu Oct 09 17:54:35 2014 -0700 |
committer | Mike Frysinger <vapier@google.com> | Wed Sep 14 00:19:44 2016 -0400 |
tree | 64d3150bea0efd2989a22f28e750c09614f9e772 | |
parent | 7a77c16d376f504bd06d017ba10c91e3a6073b08 [diff] |
When syncing a project with a shared object store, disable automatic pruning. The shared object stores confuse git and make it throw away objects which are still in use. We'll avoid that problem by disabling automatic pruning on those projects, but there's nothing preventing a user from changing the config back or pruning a repository manually. BUG=chromium:375945 TEST=Ran repo sync on fresh ChromeOS checkout, starting with a branch of repo with this change. Verified that the kernel projects and no others were identified as having shared object stores, and that repo successfully disabled automatic pruning in their configs. Re-enabled pruning and ran repo sync just on one of the kernel directories. Verified that pruning was re-disabled as a result. Change-Id: I728ed5b06f0087aeb5a23ba8f5410a7cd10af5b0
Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.