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

Hadoop QA commented on HDFS-12110:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue}  0m  
2s{color} | {color:blue} The patch file was not named according to hadoop's 
naming conventions. Please see https://wiki.apache.org/hadoop/HowToContribute 
for instructions. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  5s{color} 
| {color:red} HDFS-12110 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-12110 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12890021/HDFS-12110.diff |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/21486/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> libhdfs++: Rebase 8707 branch onto an up to date version of trunk
> -----------------------------------------------------------------
>
>                 Key: HDFS-12110
>                 URL: https://issues.apache.org/jira/browse/HDFS-12110
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: James Clampffer
>            Assignee: Deepak Majeti
>         Attachments: HDFS-12110.diff, HDFS-12110.HDFS-8707.000.patch
>
>
> It's been way too long since this has been done and it's time to start 
> knocking down blockers for merging into trunk.  Can most likely just 
> copy/paste the libhdfs++ directory into a newer version of master.  Want to 
> track it in a jira since it's likely to cause conflicts when pulling the 
> updated branch for the first time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to