<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tools/git-repo.git, branch v2.43</title>
<subtitle>Mirror of gerrit.googlesource.com/git-repo</subtitle>
<id>https://git.enea.com/cgit/tools/git-repo.git/atom?h=v2.43</id>
<link rel='self' href='https://git.enea.com/cgit/tools/git-repo.git/atom?h=v2.43'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/'/>
<updated>2024-03-07T17:21:51+00:00</updated>
<entry>
<title>sync: introduce --force-checkout</title>
<updated>2024-03-07T17:21:51+00:00</updated>
<author>
<name>Josip Sokcevic</name>
<email>sokcevic@google.com</email>
</author>
<published>2024-02-29T17:48:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=edadb25c0270398e9afa3eb0093d6b94aa51c3f4'/>
<id>urn:sha1:edadb25c0270398e9afa3eb0093d6b94aa51c3f4</id>
<content type='text'>
In some cases (e.g. in a CI system), it's desirable to be able to
instruct repo to force checkout. This flag passes --force flag to `git
checkout` operations.

Bug: b/327624021
Change-Id: I579edda546fb8147c4e1a267e2605fcf6e597421
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/411518
Commit-Queue: Josip Sokcevic &lt;sokcevic@google.com&gt;
Reviewed-by: Gavin Mak &lt;gavinmak@google.com&gt;
Reviewed-by: George Engelbrecht &lt;engeg@google.com&gt;
Tested-by: Josip Sokcevic &lt;sokcevic@google.com&gt;
</content>
</entry>
<entry>
<title>upload: Add support for setting patchset description</title>
<updated>2024-03-04T18:50:24+00:00</updated>
<author>
<name>Sergiy Belozorov</name>
<email>sergiyb@chromium.org</email>
</author>
<published>2024-03-04T18:48:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=96edb9b573d6c58b1990090c467ce0c2809bc0b1'/>
<id>urn:sha1:96edb9b573d6c58b1990090c467ce0c2809bc0b1</id>
<content type='text'>
Bug: 308467447
Change-Id: I7abcbc98131b826120fc9ab85d5b889f90db4b0a
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/355968
Tested-by: Sergiy Belozorov &lt;sergiyb@chromium.org&gt;
Reviewed-by: Mike Frysinger &lt;vapier@google.com&gt;
Commit-Queue: Sergiy Belozorov &lt;sergiyb@chromium.org&gt;
</content>
</entry>
<entry>
<title>sync: Introduce git checkout levels</title>
<updated>2024-02-27T17:28:33+00:00</updated>
<author>
<name>Josip Sokcevic</name>
<email>sokcevic@google.com</email>
</author>
<published>2024-02-23T00:38:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=5554572f02537b8646139d59ab520e59e1d5f7b3'/>
<id>urn:sha1:5554572f02537b8646139d59ab520e59e1d5f7b3</id>
<content type='text'>
If a repo manifest is updated so that project B is placed within a
project A, and if project A had content in new B's location in the old
checkout, then repo sync could break depending on checkout order, since
B can't be checked out before A.

This change introduces checkout levels which enforces right sequence of
checkouts while still allowing for parallel checkout. In an example
above, A will always be checked out first before B.

BUG=b:325119758
TEST=./run_tests, manual sync on ChromeOS repository

Change-Id: Ib3b5e4d2639ca56620a1e4c6bf76d7b1ab805250
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/410421
Tested-by: Josip Sokcevic &lt;sokcevic@google.com&gt;
Reviewed-by: Greg Edelston &lt;gredelston@google.com&gt;
Commit-Queue: Josip Sokcevic &lt;sokcevic@google.com&gt;
Reviewed-by: Gavin Mak &lt;gavinmak@google.com&gt;
</content>
</entry>
<entry>
<title>git_command: Return None from GetEventTargetPath() if set to empty string</title>
<updated>2024-02-26T17:51:11+00:00</updated>
<author>
<name>Peter Collingbourne</name>
<email>pcc@google.com</email>
</author>
<published>2024-02-24T03:18:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=97ca50f5f946c39e8ecd00c7e6ea78e90b4bb6dd'/>
<id>urn:sha1:97ca50f5f946c39e8ecd00c7e6ea78e90b4bb6dd</id>
<content type='text'>
If trace2.eventTarget was set to the empty string,
match git behavior and don't write a trace.

Bug: 319673783
Change-Id: I02b3884ad97551f8a9d7363c2cbe6b0adee6f73e
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/410518
Reviewed-by: Josip Sokcevic &lt;sokcevic@google.com&gt;
Commit-Queue: Josip Sokcevic &lt;sokcevic@google.com&gt;
Tested-by: Peter Collingbourne &lt;pcc@google.com&gt;
</content>
</entry>
<entry>
<title>trace: Save trace2 sid in REPO_TRACE file</title>
<updated>2024-02-22T20:55:09+00:00</updated>
<author>
<name>Josip Sokcevic</name>
<email>sokcevic@google.com</email>
</author>
<published>2024-02-21T19:04:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=8896b68926b660a90f37a9a37221c30514c52523'/>
<id>urn:sha1:8896b68926b660a90f37a9a37221c30514c52523</id>
<content type='text'>
git-trace2 events contain additional information what git is doing under
the hood, and repo doesn't have visibility into.

Instead of relying on timestamp information to match REPO_TRACE with
git-trace2 events, add SID information into REPO_TRACE.

Change-Id: I37672a3face81858072c7a3ce34ca3379199dab5
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/410280
Tested-by: Josip Sokcevic &lt;sokcevic@google.com&gt;
Reviewed-by: Gavin Mak &lt;gavinmak@google.com&gt;
Commit-Queue: Josip Sokcevic &lt;sokcevic@google.com&gt;
</content>
</entry>
<entry>
<title>subcmds: sync: Remove deprecated _AUTO_GC</title>
<updated>2024-02-20T19:55:15+00:00</updated>
<author>
<name>Greg Edelston</name>
<email>gredelston@google.com</email>
</author>
<published>2024-02-20T17:07:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=fec8cd6704b8ca7e01ed2de9d8757a2afd35188b'/>
<id>urn:sha1:fec8cd6704b8ca7e01ed2de9d8757a2afd35188b</id>
<content type='text'>
Opportunistic cleanup. It looks like this deprecated feature was slated
for deletion nearly a year ago.

Bug: None
Test: ./run_tests
Change-Id: I0bd0c0e6acbd1eaee1c0b4945c79038257d22f44
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/410198
Reviewed-by: Yiwei Zhang &lt;yiwzhang@google.com&gt;
Commit-Queue: Greg Edelston &lt;gredelston@google.com&gt;
Tested-by: Greg Edelston &lt;gredelston@google.com&gt;
</content>
</entry>
<entry>
<title>launcher: Set shebang to python3</title>
<updated>2024-02-07T20:44:32+00:00</updated>
<author>
<name>Josip Sokcevic</name>
<email>sokcevic@google.com</email>
</author>
<published>2024-02-06T22:25:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=b8139bdcf87540fbe88a8b9180c052f5cc3a91b7'/>
<id>urn:sha1:b8139bdcf87540fbe88a8b9180c052f5cc3a91b7</id>
<content type='text'>
Some (most?) Linux repos don't have /usr/bin/python, unless
python-is-python3 is installed. While package owners can adjust shebang,
we have seen an increase in number of bugs filed as extra steps are
required.

Per PEP-0394, python3 is acceptable and should be available if python3
is supported. We no longer support python2, and repo no longer works
with python2, so this change makes that explicit.

Bug: 40014585
Change-Id: I9aed90fd470ef601bd33bd596af3df69da69ef5d
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/407497
Commit-Queue: Josip Sokcevic &lt;sokcevic@google.com&gt;
Reviewed-by: Jason Chang &lt;jasonnc@google.com&gt;
Reviewed-by: Gavin Mak &lt;gavinmak@google.com&gt;
Reviewed-by: Максим Паймушкин &lt;maxim.paymushkin@gmail.com&gt;
Tested-by: Josip Sokcevic &lt;sokcevic@google.com&gt;
</content>
</entry>
<entry>
<title>sync: ensure RepoChangedException propagated</title>
<updated>2024-02-06T18:46:19+00:00</updated>
<author>
<name>Jason Chang</name>
<email>jasonnc@google.com</email>
</author>
<published>2024-02-05T23:15:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=26fa3180fbe2380ff20eb94171074d833b210b45'/>
<id>urn:sha1:26fa3180fbe2380ff20eb94171074d833b210b45</id>
<content type='text'>
Prior to this change RepoChangedException would be caught and re-rasied
as a different exception. This would prevent RepoChangedException
handler from running in main.py

Bug: b/323232806
Change-Id: I9055ff95d439d6ff225206c5bf1755cc718bcfcc
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/407144
Tested-by: Josip Sokcevic &lt;sokcevic@google.com&gt;
Reviewed-by: Josip Sokcevic &lt;sokcevic@google.com&gt;
Commit-Queue: Josip Sokcevic &lt;sokcevic@google.com&gt;
</content>
</entry>
<entry>
<title>stop passing project to UpdateManifestError</title>
<updated>2024-02-02T18:35:13+00:00</updated>
<author>
<name>Yiwei Zhang</name>
<email>yiwzhang@google.com</email>
</author>
<published>2023-12-20T20:39:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=d379e77f44d11da1ab817f3796f9559f163c1b0f'/>
<id>urn:sha1:d379e77f44d11da1ab817f3796f9559f163c1b0f</id>
<content type='text'>
UpdateManifestError inherits from RepoExitError which inherits
from BaseRepoError. None of them takes project as kwargs
causing the error like "UpdateManifestError() takes no keyword
arguments" in b/317183321

[1]: https://gerrit.googlesource.com/git-repo/+/449b23b698d7d4b13909667a49a0698eb495eeaa/error.py#144

Bug: b/317183321
Change-Id: I64c3dc502027f9dda56a0824f2712364b4502934
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/398997
Commit-Queue: Yiwei Zhang &lt;yiwzhang@google.com&gt;
Tested-by: Yiwei Zhang &lt;yiwzhang@google.com&gt;
Reviewed-by: Josip Sokcevic &lt;sokcevic@google.com&gt;
Reviewed-by: Jason Chang &lt;jasonnc@google.com&gt;
</content>
</entry>
<entry>
<title>project: Rename if deletion fails</title>
<updated>2024-01-25T21:32:58+00:00</updated>
<author>
<name>Josip Sokcevic</name>
<email>sokcevic@google.com</email>
</author>
<published>2024-01-24T21:54:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=4217a82bec7b95c1a0bc7b081a1764a6a6d6c59b'/>
<id>urn:sha1:4217a82bec7b95c1a0bc7b081a1764a6a6d6c59b</id>
<content type='text'>
If a project contains files not owned by the current user, remove will
fail. In order to ensure repo sync continues to work, rename the
affected project instead, and let user know about it.

Bug: 321273512
Change-Id: I0779d61fc67042308a0226adea7d98167252a5d3
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/404372
Reviewed-by: Mike Frysinger &lt;vapier@google.com&gt;
Tested-by: Josip Sokcevic &lt;sokcevic@google.com&gt;
Commit-Queue: Josip Sokcevic &lt;sokcevic@google.com&gt;
</content>
</entry>
</feed>
