Issue 871: add cherry-picked commit as last patch set
Status:  Submitted
Owner:
Closed:  Oct 2011

Blocking:
issue 1023
Reported by peter.ni...@googlemail.com, Mar 7, 2011
related to projects using the cherry-pick commit policy

It would be nice to see the final cherry-picked commit(that was created when hitting the submit button) as the last patch set within the stack of patch sets for a change request
May 19, 2011
Project Member #1 nas...@grainawi.org
(No comment was entered for this change.)
Blocking: 868
May 19, 2011
Project Member #2 nas...@grainawi.org
(No comment was entered for this change.)
Blocking: 827
May 20, 2011
#4 sop@google.com
 Issue 827  has been merged into this issue.
May 20, 2011
#5 sop@google.com
(No comment was entered for this change.)
Blocking: -827
May 20, 2011
#6 sop@google.com
 Issue 868  has been merged into this issue.
May 20, 2011
#7 sop@google.com
(No comment was entered for this change.)
Blocking: -868
Jun 27, 2011
Project Member #8 bklarson@gmail.com
(No comment was entered for this change.)
Blocking: 1023
Oct 26, 2011
Project Member #9 bklarson@gmail.com
(No comment was entered for this change.)
Status: Started
Owner: bklarson@gmail.com
Oct 27, 2011
Project Member #10 bklarson@gmail.com
(No comment was entered for this change.)
Status: Fixed
Labels: FixedIn-2.2.2
Oct 27, 2011
Project Member #11 bklarson@gmail.com
Sorry, too eager to change states.
Status: Submitted
Feb 2, 2012
#12 imsan...@gmail.com
This does not work for me in 2.2.2

With 2.2.2 i'm getting even less information than in 2.2.1

Message in 2.2.2
Change has been successfully cherry-picked

Message in 2.2.1
Change has been successfully cherry-picked as $COMMIT_ID.
Feb 8, 2012
Project Member #13 bklarson@gmail.com
Sorry this was mis-labeled.  The change to add a new patch set when the change is submitted wasn't in time for 2.2.2, but will be included in 2.2.3.  I'm not sure why the behavior is different with 2.2.2.
Labels: -FixedIn-2.2.2 FixedIn-2.2.3