<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tools/git-repo.git/subcmds/selfupdate.py, branch v2.5</title>
<subtitle>Mirror of gerrit.googlesource.com/git-repo</subtitle>
<id>https://git.enea.com/cgit/tools/git-repo.git/atom?h=v2.5</id>
<link rel='self' href='https://git.enea.com/cgit/tools/git-repo.git/atom?h=v2.5'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/'/>
<updated>2020-02-19T00:24:43+00:00</updated>
<entry>
<title>avoid negative variables</title>
<updated>2020-02-19T00:24:43+00:00</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@google.com</email>
</author>
<published>2020-02-17T19:36:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=c58ec4dba102d88fec67e833eb8421202eb4c1ea'/>
<id>urn:sha1:c58ec4dba102d88fec67e833eb8421202eb4c1ea</id>
<content type='text'>
Trying to use booleans with names like "no_xxx" are hard to follow due
to the double negatives.  Invert all of them so we only have positive
meanings to follow.

Change-Id: Ifd37d0368f97034d94aa2cf38db52c723ac0c6ed
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/255493
Tested-by: Mike Frysinger &lt;vapier@google.com&gt;
Reviewed-by: David Pursehouse &lt;dpursehouse@collab.net&gt;
</content>
</entry>
<entry>
<title>Fix blank line issues reported by flake8</title>
<updated>2020-02-12T06:36:40+00:00</updated>
<author>
<name>David Pursehouse</name>
<email>dpursehouse@collab.net</email>
</author>
<published>2020-02-12T06:20:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=819827a42ddb364f98c3a1a7eae2536dc54bc4cc'/>
<id>urn:sha1:819827a42ddb364f98c3a1a7eae2536dc54bc4cc</id>
<content type='text'>
- E301 expected 1 blank line
- E302 expected 2 blank lines
- E303 too many blank lines
- E305 expected 2 blank lines after class or function definition
- E306 expected 1 blank line before a nested definition

Fixed automatically with autopep8:

  git ls-files | grep py$ | xargs autopep8 --in-place \
    --select E301,E302,E303,E305,E306

Manually fix issues in project.py caused by misuse of block comments.

Change-Id: Iee840fcaff48aae504ddac9c3e76d2acd484f6a9
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/254599
Reviewed-by: Mike Frysinger &lt;vapier@google.com&gt;
Tested-by: David Pursehouse &lt;dpursehouse@collab.net&gt;
</content>
</entry>
<entry>
<title>Fix flake8 E251 unexpected spaces around keyword / parameter equals</title>
<updated>2020-02-12T05:17:08+00:00</updated>
<author>
<name>David Pursehouse</name>
<email>dpursehouse@collab.net</email>
</author>
<published>2020-02-12T04:56:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=e5913ae41058ddd7f692e9cc18e5f71b8251bd60'/>
<id>urn:sha1:e5913ae41058ddd7f692e9cc18e5f71b8251bd60</id>
<content type='text'>
Fixed automatically with autopep8:

  git ls-files | grep py$ | xargs autopep8 --in-place --select E251

Change-Id: I58009e1c8c91c39745d559ac919be331d4cd9e77
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/254598
Tested-by: David Pursehouse &lt;dpursehouse@collab.net&gt;
Reviewed-by: Mike Frysinger &lt;vapier@google.com&gt;
</content>
</entry>
<entry>
<title>set default file encoding to utf-8</title>
<updated>2019-06-13T14:30:52+00:00</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@google.com</email>
</author>
<published>2019-06-13T06:30:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=f601376e13e6beca7ab8d660e00d6c14714f305f'/>
<id>urn:sha1:f601376e13e6beca7ab8d660e00d6c14714f305f</id>
<content type='text'>
There's no reason to support any other encoding in these files.
This only affects the files themselves and not streams they open.

Bug: https://crbug.com/gerrit/10418
Change-Id: I053cb40cd3666ce5c8a0689b9dd938f24ca765bf
</content>
</entry>
<entry>
<title>Change print statements to work in python3</title>
<updated>2012-11-14T01:33:56+00:00</updated>
<author>
<name>Sarah Owens</name>
<email>sarato@inkylabs.com</email>
</author>
<published>2012-11-02T05:59:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=cecd1d864fc3cf02cf50d367111e0d0e173c5dc6'/>
<id>urn:sha1:cecd1d864fc3cf02cf50d367111e0d0e173c5dc6</id>
<content type='text'>
This is part of a series of changes to introduce Python3 support.

Change-Id: I373be5de7141aa127d7debdbce1df39148dbec32
</content>
</entry>
<entry>
<title>sync: Run `git gc --auto` after fetch</title>
<updated>2011-01-10T01:39:22+00:00</updated>
<author>
<name>Shawn O. Pearce</name>
<email>sop@google.com</email>
</author>
<published>2009-07-03T22:22:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=0d2b61f11d0501fcf1e5a1c19f18dac03e0b09bc'/>
<id>urn:sha1:0d2b61f11d0501fcf1e5a1c19f18dac03e0b09bc</id>
<content type='text'>
Users may wind up with a lot of loose object content in projects they
don't frequently make changes in, but that are modified by others.

Since we bypass many git code paths that would have otherwise called
out to `git gc --auto`, its possible for these projects to have
their loose object database grow out of control.  To help prevent
that, we now invoke it ourselves during the network half of sync.

Signed-off-by: Shawn O. Pearce &lt;sop@google.com&gt;
(cherry picked from commit 1875ddd47c0bf38e5cc52e1e5875caabce2d8742)
</content>
</entry>
<entry>
<title>Clarify options that control the repo executable version</title>
<updated>2009-04-18T18:28:57+00:00</updated>
<author>
<name>Shawn O. Pearce</name>
<email>sop@google.com</email>
</author>
<published>2009-04-18T18:28:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=fd89b67f5c3ad94f050509e1421c73aff380c0a7'/>
<id>urn:sha1:fd89b67f5c3ad94f050509e1421c73aff380c0a7</id>
<content type='text'>
Signed-off-by: Shawn O. Pearce &lt;sop@google.com&gt;
</content>
</entry>
<entry>
<title>Add 'repo selfupdate' to upgrade only repo</title>
<updated>2009-04-13T18:53:53+00:00</updated>
<author>
<name>Shawn O. Pearce</name>
<email>sop@google.com</email>
</author>
<published>2009-04-13T18:51:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=e756c412e35b9ac1a126985d4d047dbd52f29277'/>
<id>urn:sha1:e756c412e35b9ac1a126985d4d047dbd52f29277</id>
<content type='text'>
Users may want to upgrade only repo to the latest release, but
leave their working tree state alone and avoid 'repo sync'.

Signed-off-by: Shawn O. Pearce &lt;sop@google.com&gt;
</content>
</entry>
</feed>
