Age | Commit message (Collapse) | Author | Files | Lines |
|
Recently some new developers accidentally used "resubmit", intending to
upload a new revision of their change, but it actually always creates a
new gerrit change.
4e15809a78ea3c6062e20e439cf8df3d06cd8569 claims that "resubmit creates a
new Change-Id for the current change and thus allow to submit changes for
review on release branches that were already reviewed on master", but
that is not actually required with gerrit versions that were in use in
the recent years, gerrit is capable of tracking Change-Id per branch.
Change-Id: I66eda4dbc6f4ff1e235105b3f55041cda88a6b60
|
|
- ./logerrit testfeature will trigger a testbuild of the
current feature branch as it is on gerrit
- ./logerrit testfeature $BRANCH will do the same for $BRANCH
- cloning to a tempdir and rm -rf'ing around isnt ideal, so
consider this as a template for your own scripting
Change-Id: I50a3c80748af82d855522f245ddbff227c8adab2
|
|
Change-Id: Ic8196ebfeef64270fcd42b44e485a2618472f184
Reviewed-on: https://gerrit.libreoffice.org/11788
Reviewed-by: Samuel Mehrbrodt <s.mehrbrodt@gmail.com>
Tested-by: Samuel Mehrbrodt <s.mehrbrodt@gmail.com>
|
|
Change-Id: I44dee045cef9227b62666ed08206a342fe37b18c
|
|
|
|
- twas more of a proof-of-concept anyway
- its more clumsy than both:
- git-review https://wiki.documentfoundation.org/Development/GitReview
- or simply using the web UI
Change-Id: Id7a11fcdaf95386c451d0e6421d32de7d1d02721
Reviewed-on: https://gerrit.libreoffice.org/3070
Reviewed-by: Thorsten Behrens <tbehrens@suse.com>
Tested-by: Thorsten Behrens <tbehrens@suse.com>
|
|
Change-Id: I17adc7cecd5cf3757d92477dacff24e46e92caab
|
|
Change-Id: I058a0b445f8b7f286ed4c22d40c0770d435d0e40
|
|
Change-Id: I2478ef0f886867c2d2247febf1b29b90fd32e5e7
|
|
Change-Id: I5f52d9c81c28c9a4b23eaf043e7b67b1fc6d82d9
|
|
Change-Id: Id041aa5a8fbb06626b7310aa76471db993b53cf0
|
|
Change-Id: Id9abc3ab45af8b6e44904090e179ce67a3f45796
Reviewed-on: https://gerrit.libreoffice.org/2541
Reviewed-by: Thomas Arnhold <thomas@arnhold.org>
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>
|
|
It printed help of the plain gerrit tool which always confused me :-)
Change-Id: Ied81688ada4b536486d998709230fc24fa3c9b62
|
|
Change-Id: Ibd21dfdb76536ea0e0a71791a91ec87e31d49960
|
|
Change-Id: I0d6f3f5521d32dad1ffaa8675d5f43c7d7fa7cea
Reviewed-on: https://gerrit.libreoffice.org/409
Reviewed-by: Jean-Tiare Le Bigot <admin@jtlebi.fr>
Reviewed-by: Tomáš Chvátal <tchvatal@suse.cz>
Tested-by: Tomáš Chvátal <tchvatal@suse.cz>
|
|
resubmit creates a new Change-Id for the current change and thus allow to submit
changes for review on release branches that were already reviewed on master.
Also hint advanced users to 'git review' which requires some more setup, but
should make things easier for regular users.
Getting this functionality into 'git review' would be likely help adoption too
-- and in python there is some sane errorchecking possible.
Change-Id: Ibea6bbfe747af160728b838c6ee236fd8f89671d
|
|
Change-Id: I12b03bb778da712cfe48543949d9634be5221419
|
|
Change-Id: I0fb8b1e4f14e153adae7a2ec1b3adbb0dab5c847
|
|
* ./logerrit review did not resolve the ChangeId to a SHA
* ./logerrit did still echo the command instead of executing it.
Change-Id: Ie4f8630f7a83134d6eb7992f4a61b5d3faf7e138
|
|
Change-Id: Icf5facbb59cba2116ae3fc6bdfc035673cf47985
|
|
Change-Id: I699aad760823a8ccbfc7dc93bf0658b5222dff71
|
|
Change-Id: I5705530ee4d5b93bc66ca23463098ac45f49323d
|