c16582058b
Recent releases of Gerrit have evolved their use of the "topic" functionality. Originally it was there merely for the convenince of users. It could be used to make a group of related or similar changes easy to query. In current releases of Gerrit, it serves a much more deliberate purpose: if submitWholeTopic is enabled, then merging one change in a topic will merge all of them simultaneously. Since this has very significant impacts to developer workflow, git-review should no longer set a topic unless it is explicitly requested by a user. This change alters the behavior of git-review so that it will no longer set a topic unless explicitly set by a user. It also deprecates the 'notopic' and '-T' options. They are retained for backwards compatability with existing scripts, but no longer have any effect. Change-Id: Ib83981a4952e1d6d68ebb8add11aabefbf3b2a4b
16 lines
569 B
YAML
16 lines
569 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Git-review no longer supplies a default topic when uploading a new
|
|
change. The only way to set a topic on a newly uploaded change is
|
|
to use the ``-t <topic>`` option.
|
|
- |
|
|
When downloading changes using ``git-review -d``, the local branch
|
|
name is now based on the change number rather than the author and
|
|
topic.
|
|
deprecations:
|
|
- |
|
|
The ``gitreview.notopic`` configuration setting and ``-T`` command line
|
|
option are deprecated and no longer have any effect. The default behavior
|
|
is now as if ``notopic`` is set.
|