Mirror of gerrit.googlesource.com/git-repo https://git.enea.com/cgit/tools/git-repo.git/atom?h=v2.8 2020-03-18T00:24:43+00:00 2020-03-18T00:24:43+00:00 Mike Frysinger vapier@google.com 2020-03-14T18:35:26+00:00 urn:sha1:58ac1678e8438fd029a22365741fc57276eda404 We refer to this as "revision" in help text, and in REPO_REV envvar, so rename to --repo-rev to be consistent. We keep --repo-branch for backwards compatibility, but as a hidden option. Bug: https://crbug.com/gerrit/11045 Change-Id: I1ecc282fba32917ed78a63850360c08469db849a Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/259352 Tested-by: Mike Frysinger <vapier@google.com> Reviewed-by: David Pursehouse <dpursehouse@collab.net> 2020-02-12T00:27:59+00:00 Mike Frysinger vapier@google.com 2020-02-11T23:43:34+00:00 urn:sha1:3645bd24200b0f97eaeb8f65552ec67cc5a3fce8 Going purely on upstream package release cycles doesn't tell the whole story: a lot of people run LTS distros which will have older versions of software we want to support. Build out a table for us to quickly reference when making decisions as to what versions of git/python we want to support, and when we can drop them. This will also help to refer users to as why we made a specific decision that might be affecting them. Change-Id: I7aea24bbefd50e358aeacf11e8c15a346c8fb8a9 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/254572 Tested-by: Mike Frysinger <vapier@google.com> Reviewed-by: David Pursehouse <dpursehouse@collab.net> 2019-06-13T03:18:10+00:00 Mike Frysinger vapier@google.com 2018-12-12T08:34:28+00:00 urn:sha1:a26c49ead4d4b1fdd71d91ebf997079f7acefc99 Change-Id: I884639665c020338ec9ceeb1add5c3b862583674