| Issue 1664: | Reverting a Change does not preserve the parent's Topic | |
| 1 person starred this issue and may be notified of changes. | Back to list |
************************************************************ ***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW ***** ***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL ***** ***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC. ***** ***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS! ***** ************************************************************ Affected Version: 2.5 What steps will reproduce the problem? 1.Push a change to refs/for/branch/TOPIC 2.Revert the change What is the expected output? What do you see instead? The revert operation generates a new change. The new change should have the same topic as the parent change. Instead, the new change has no topic. Please provide any additional information below. Our patchset-created hook makes some automated review decisions based on the topic. When changes are created without a topic, the hook 'fails' the change automatically, requiring administrative intervention. Our current solution involves parsing the commit message of the revert change, which is not ideal.
Nov 16, 2012
Project Member
#1
david.pu...@sonymobile.com
Nov 16, 2012
(No comment was entered for this change.)
Status:
ChangeUnderReview
Nov 16, 2012
(No comment was entered for this change.)
Status:
Submitted
Nov 17, 2012
(No comment was entered for this change.)
Labels:
FixedIn-2.6
|
|
| ► Sign in to add a comment |