[
https://issues.apache.org/jira/browse/IMPALA-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462985#comment-16462985
]
Philip Zeyliger commented on IMPALA-6967:
-----------------------------------------
Let's say I have a conflicting patch that I need to go in two branches. I don't
think it's a good idea for me to confuse the commit message by saying
"Cherry-picks: not for 2.x".
> GVO should only allow patches that apply cleanly to both master and 2.x
> -----------------------------------------------------------------------
>
> Key: IMPALA-6967
> URL: https://issues.apache.org/jira/browse/IMPALA-6967
> Project: IMPALA
> Issue Type: Task
> Components: Infrastructure
> Reporter: Sailesh Mukil
> Priority: Major
> Labels: jenkins
>
> Following this thread:
> https://lists.apache.org/thread.html/bba3c5a87635ad3c70c40ac120de2ddb41c3d0e2f5db0b29bc0243ff@%3Cdev.impala.apache.org%3E
> It would take load off authors if the GVO could automatically tell if a patch
> that's being pushed to master would cleanly cherry-pick to 2.x.
> At the beginning of the GVO, we should try to cherry-pick to 2.x and fail if
> there are conflicts, unless the commit message has the line:
> "Cherry-picks: not for 2.x"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
