<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tools/git-repo.git/subcmds, branch v2.6</title>
<subtitle>Mirror of gerrit.googlesource.com/git-repo</subtitle>
<id>https://git.enea.com/cgit/tools/git-repo.git/atom?h=v2.6</id>
<link rel='self' href='https://git.enea.com/cgit/tools/git-repo.git/atom?h=v2.6'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/'/>
<updated>2020-04-14T06:49:31+00:00</updated>
<entry>
<title>forall.py: Close file after removing the stream</title>
<updated>2020-04-14T06:49:31+00:00</updated>
<author>
<name>Karsten Pfeiffer-Raddatz</name>
<email>raddatz.karsten@gmail.com</email>
</author>
<published>2020-04-13T11:48:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=d086467012e1970f44f27b67b4296a2a6fb097d5'/>
<id>urn:sha1:d086467012e1970f44f27b67b4296a2a6fb097d5</id>
<content type='text'>
In order to remove the stream fileno() will be called on the filedescriptor.
If the file is already closed fileno() will raise an error and forall
will fail.

Bug: https://crbug.com/gerrit/12563
Change-Id: Ib7b895fe881c844e3eb3672b011fdcdbdae63024
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/262838
Reviewed-by: David Pursehouse &lt;dpursehouse@collab.net&gt;
Tested-by: Karsten Pfeiffer-Raddatz &lt;raddatz.karsten@gmail.com&gt;
</content>
</entry>
<entry>
<title>sync: add retry to fetch operations</title>
<updated>2020-04-02T21:17:54+00:00</updated>
<author>
<name>George Engelbrecht</name>
<email>engeg@google.com</email>
</author>
<published>2020-04-02T18:36:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=9bc283e49bcb2663dc8c06a4efad289a3683aaa4'/>
<id>urn:sha1:9bc283e49bcb2663dc8c06a4efad289a3683aaa4</id>
<content type='text'>
Add retries with exponential backoff and jitter to the fetch
operations. By default don't change behavior and enable
behind the new flag '--fetch-retries'.

Bug: https://crbug.com/1061473

Change-Id: I492710843985d00f81cbe3402dc56f2d21a45b35
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/261576
Reviewed-by: Mike Frysinger &lt;vapier@google.com&gt;
Tested-by: George Engelbrecht &lt;engeg@google.com&gt;
</content>
</entry>
<entry>
<title>version: include tag commit date for easy reference</title>
<updated>2020-03-31T03:27:57+00:00</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@google.com</email>
</author>
<published>2020-03-30T22:51:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=b4a6f6d7981fb6f4861485381b0b5ee761ab3ae8'/>
<id>urn:sha1:b4a6f6d7981fb6f4861485381b0b5ee761ab3ae8</id>
<content type='text'>
This is more for users trying to get a sense of how old/new their
current version of repo is when debugging issues.

Change-Id: Ifb413c679bb8c8dbf4f9334137adf086bb000a68
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/261192
Reviewed-by: Jonathan Nieder &lt;jrn@google.com&gt;
Tested-by: Mike Frysinger &lt;vapier@google.com&gt;
</content>
</entry>
<entry>
<title>version: fix running under Python 2</title>
<updated>2020-03-25T04:56:07+00:00</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@google.com</email>
</author>
<published>2020-03-23T20:55:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=e257d5666568a9621b7dfece313c705e41e17070'/>
<id>urn:sha1:e257d5666568a9621b7dfece313c705e41e17070</id>
<content type='text'>
This gets the unittests passing again for now.

Change-Id: Ibed430a305bc26b907ad0ea424c7eec7de37e942
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/259994
Tested-by: Mike Frysinger &lt;vapier@google.com&gt;
Reviewed-by: Jonathan Nieder &lt;jrn@google.com&gt;
</content>
</entry>
<entry>
<title>init: respect --repo-rev changes</title>
<updated>2020-03-25T04:55:50+00:00</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@google.com</email>
</author>
<published>2020-02-29T07:53:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=3599cc397581086b7fddcd2e07308bfdac7751b1'/>
<id>urn:sha1:3599cc397581086b7fddcd2e07308bfdac7751b1</id>
<content type='text'>
We respect this option when running the first `repo init`, but then
silently ignore it once the initial sync is done.  Make sure users
are able to change things on the fly.

We refactor the wrapper API to allow reuse between the two init's.

Bug: https://crbug.com/gerrit/11045
Change-Id: Icb89a8cddca32f39a760a6283152457810b2392d
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/260032
Tested-by: Mike Frysinger &lt;vapier@google.com&gt;
Reviewed-by: Jonathan Nieder &lt;jrn@google.com&gt;
</content>
</entry>
<entry>
<title>download: add a --branch option</title>
<updated>2020-03-23T00:31:10+00:00</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@google.com</email>
</author>
<published>2020-03-22T17:54:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=78964472adc5c92e0aad7bf513c50df5331d9d66'/>
<id>urn:sha1:78964472adc5c92e0aad7bf513c50df5331d9d66</id>
<content type='text'>
This allows people to quickly create new branches when pulling down
changes rather than having to juggle the git calls themselves.

Bug: https://crbug.com/gerrit/11609
Change-Id: Ie6a4d05e9f4e9347fe7f7119c768e6446563ae65
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/259855
Reviewed-by: David Pursehouse &lt;dpursehouse@collab.net&gt;
Tested-by: Mike Frysinger &lt;vapier@google.com&gt;
</content>
</entry>
<entry>
<title>download: unify error handling with sub git calls</title>
<updated>2020-03-23T00:28:54+00:00</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@google.com</email>
</author>
<published>2020-03-22T17:36:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=05097c622231eeb095c17c5f5c4e791c57f382bc'/>
<id>urn:sha1:05097c622231eeb095c17c5f5c4e791c57f382bc</id>
<content type='text'>
We gracefully handle cherry-pick errors, but none of the others
which means people get confusing Python tracebacks.  Move the
main logic in a single GitError try block so we can show pretty
error messages for all of them.

Change-Id: I52cdf6468d21a98de7f65b86d5267b3caabd5af8
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/259854
Reviewed-by: David Pursehouse &lt;dpursehouse@collab.net&gt;
Tested-by: Mike Frysinger &lt;vapier@google.com&gt;
</content>
</entry>
<entry>
<title>download: support -x when cherry-picking</title>
<updated>2020-03-23T00:27:52+00:00</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@google.com</email>
</author>
<published>2020-03-22T16:15:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=915fda130efa14b9314b500d122f9af707518508'/>
<id>urn:sha1:915fda130efa14b9314b500d122f9af707518508</id>
<content type='text'>
This is a pretty common option for people to want too use, so include
it as a pass-thru option when cherry-picking.

Bug: https://crbug.com/gerrit/9418
Change-Id: I2a24c1ed7544541719caa4d3c0574347a151a1b0
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/259853
Reviewed-by: David Pursehouse &lt;dpursehouse@collab.net&gt;
Tested-by: Mike Frysinger &lt;vapier@google.com&gt;
</content>
</entry>
<entry>
<title>download: support --ff when cherry-picking</title>
<updated>2020-03-23T00:26:26+00:00</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@google.com</email>
</author>
<published>2020-03-22T16:14:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=ea43176de0a46eadb12be814517532a13eec8b1d'/>
<id>urn:sha1:ea43176de0a46eadb12be814517532a13eec8b1d</id>
<content type='text'>
The git cherry-pick already supports this, so plumb the existing repo
option down.  Otherwise it's confusing when people use -c --ff and it
doesn't use that behavior.

Change-Id: Id68932ffa09204bb30b92a21aff185c00394a520
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/259852
Reviewed-by: David Pursehouse &lt;dpursehouse@collab.net&gt;
Tested-by: Mike Frysinger &lt;vapier@google.com&gt;
</content>
</entry>
<entry>
<title>init: rename --repo-branch to --repo-rev</title>
<updated>2020-03-18T00:24:43+00:00</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@google.com</email>
</author>
<published>2020-03-14T18:35:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=58ac1678e8438fd029a22365741fc57276eda404'/>
<id>urn:sha1:58ac1678e8438fd029a22365741fc57276eda404</id>
<content type='text'>
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 &lt;vapier@google.com&gt;
Reviewed-by: David Pursehouse &lt;dpursehouse@collab.net&gt;
</content>
</entry>
</feed>
