commit | c5b172ad6f65e573193a555806bd912b2582ab56 | [log] [tgz] |
---|---|---|
author | Mike Frysinger <vapier@google.com> | Wed Jul 31 17:34:23 2019 -0400 |
committer | Mike Frysinger <vapier@google.com> | Thu Aug 01 04:06:04 2019 +0000 |
tree | 6bf1ace5cb3f448f6e15c960677b3d26d28106f8 | |
parent | 87deaefd86e14518635cf69d8318a38dacf656ab [diff] |
manifest-format: clarify <copyfile> & <linkfile> restrictions While we don't (yet) explicitly enforce all of these, make sure we document the expected behavior so we can all agree on it. Bug: https://crbug.com/gerrit/11218 Change-Id: Ife8298702fa445ac055ef43c6d62706a9cb199ce Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/232893 Reviewed-by: David Pursehouse <dpursehouse@collab.net> Tested-by: Mike Frysinger <vapier@google.com>
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.