You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Vinod K V (JIRA)" <ji...@apache.org> on 2010/04/30 08:22:55 UTC

[jira] Created: (HADOOP-6740) Move commands_manual.xml from mapreduce into common

Move commands_manual.xml from mapreduce into common
---------------------------------------------------

                 Key: HADOOP-6740
                 URL: https://issues.apache.org/jira/browse/HADOOP-6740
             Project: Hadoop Common
          Issue Type: Bug
          Components: documentation
    Affects Versions: 0.21.0
            Reporter: Vinod K V
            Assignee: Tom White
             Fix For: 0.21.0


Long term, we want to split the commands manual separately into the sub-projects (MAPEDUCE-1079). But for 0.21 atleast we can move it into common. Having it in mapreduce is definitely inconvenient.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (HADOOP-6740) Move commands_manual.xml from mapreduce into common

Posted by "Tom White (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White resolved HADOOP-6740.
-------------------------------

    Resolution: Duplicate

Fixed by HADOOP-6738 and MAPREDUCE-1404.

> Move commands_manual.xml from mapreduce into common
> ---------------------------------------------------
>
>                 Key: HADOOP-6740
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6740
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 0.21.0
>            Reporter: Vinod K V
>            Assignee: Tom White
>            Priority: Blocker
>             Fix For: 0.21.0
>
>
> Long term, we want to split the commands manual separately into the sub-projects (MAPEDUCE-1079). But for 0.21 atleast we can move it into common. Having it in mapreduce is definitely inconvenient.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.