Daniel Sandler 4c50deea28 Fail sync when encountering "N commits behind."
This is almost always something the user needs to address
before continuing work, so promoting it to a failure (rather
than simply an informational message) seems the right way to
go. As a side-effect, repo will now exit with a non-zero
status code in this situation, so pipelines of the form
`repo sync && make` will fail if there are branches that
are stalled due to uploaded but unmerged patches.
2010-03-04 11:56:38 -05:00
2009-12-10 15:24:45 -08:00
2009-06-02 00:09:07 +02:00
2009-06-02 00:09:07 +02:00
2008-10-21 07:00:00 -07:00
2009-05-29 09:31:28 -07:00
2009-05-29 09:31:28 -07:00
Description
No description provided
Apache-2.0 35 MiB
Languages
Python 99.1%
Shell 0.9%