| commit | 9bfdfbe117d16107e07e1c376fec8eb245aab424 | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@google.com> | Mon Sep 30 22:46:45 2019 -0400 |
| committer | Mike Frysinger <vapier@google.com> | Tue Oct 01 05:47:35 2019 +0000 |
| tree | 121bf9495b48f1175f97caca0ba21e1024c10786 | |
| parent | 2f0951b216489ecbd0a28935ca589fb0067a8381 [diff] |
version: add source versions & User-Agents to the output Depending on where/how repo is invoked, the active version might be from a git tree, and it might be different from the .repo/repo.git/ version in the current repo client checkout. Report both if they're different so it's clearer. Lets also include the two different User-Agent's that we set up when talking to networked services. Bug: https://crbug.com/gerrit/11144 Change-Id: I2ebb6e3ac30e374a8406cab3e4438087246a8c57 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/239234 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.