hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7384) Allow test-patch to be more flexible about patch format
Date Mon, 13 Jun 2011 22:31:47 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048836#comment-13048836
] 

Tom White commented on HADOOP-7384:
-----------------------------------

+1 This looks like a useful change.

> Allow test-patch to be more flexible about patch format
> -------------------------------------------------------
>
>                 Key: HADOOP-7384
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7384
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hadoop-7384.txt
>
>
> Right now the test-patch process only accepts patches that are generated as "-p0" relative
to common/, hdfs/, or mapreduce/. This has always been annoying for git users where the default
patch format is -p1. It's also now annoying for SVN users who may generate a patch relative
to trunk/ instead of the subproject subdirectory. We should auto-detect the correct patch
level.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message