diff options
| author | Michael Stahl <mstahl@redhat.com> | 2016-04-26 17:22:47 +0200 |
|---|---|---|
| committer | Michael Stahl <mstahl@redhat.com> | 2016-04-27 15:52:40 +0200 |
| commit | 7895f7e1a8d12a89b69fe55326fde7b7f5a34b8f (patch) | |
| tree | ba248ddfdfb5bcd482aa1162e64bd4c54ee7a9b7 /bin/convwatch.py | |
| parent | 3585cfe5f55f3ac8131a19abc5cbbf857364de9a (diff) | |
logerrit: disarm the "resubmit" foot-gun
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
Diffstat (limited to 'bin/convwatch.py')
0 files changed, 0 insertions, 0 deletions