| Issue 2710: | ChangeScreen2: Cherry-picking a change doesn't trigger re-rendering of original change | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Affected Version: master What steps will reproduce the problem? 0. open new change screen 1. cherry-pick a change from branch foo to branch bar 2. new (target) change is opened 3. change to the original change 4. Message is missing: "This patchset was cherry picked to branch bar as commit c5ad912e0" Work around: clear browser caches. The problem seems to be that the oiginal change is not get updated and thus not re-rendred.
Jun 11, 2014
Project Member
#1
David.Os...@gmail.com
Summary:
ChangeScreen2: Cherry-picking a change doesn't trigger re-rendering of original change
(was: New change screen: Cherry-picking a change doesn't trigger re-rendering of original change )
Jun 22, 2014
(No comment was entered for this change.)
Status:
Accepted
Jun 23, 2014
(No comment was entered for this change.)
Status:
Submitted
Labels: FixedIn-2.9
Jul 18, 2014
(No comment was entered for this change.)
Status:
Released
|
|
| ► Sign in to add a comment |