| Issue 871: | add cherry-picked commit as last patch set | |
| 11 people starred this issue and may be notified of changes. | Back to list |
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
Blocking:
868
May 19, 2011
(No comment was entered for this change.)
Blocking:
827
May 19, 2011
We want to do it, discussed on the list: http://groups.google.com/group/repo-discuss/browse_thread/thread/ce57f49517023436/72172b3da19c7dfa?lnk=gst&q=question+about+gitweb#72172b3da19c7dfa
Status:
Accepted
May 20, 2011
Issue 827 has been merged into this issue.
May 20, 2011
(No comment was entered for this change.)
Blocking:
-827
May 20, 2011
Issue 868 has been merged into this issue.
May 20, 2011
(No comment was entered for this change.)
Blocking:
-868
Jun 27, 2011
(No comment was entered for this change.)
Blocking:
1023
Oct 26, 2011
(No comment was entered for this change.)
Status:
Started
Owner: bklarson@gmail.com
Oct 27, 2011
(No comment was entered for this change.)
Status:
Fixed
Labels: FixedIn-2.2.2
Oct 27, 2011
Sorry, too eager to change states.
Status:
Submitted
Feb 2, 2012
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
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
|
|
| ► Sign in to add a comment |