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

Todd Lipcon commented on HADOOP-7106:
-------------------------------------

bq. Todd, with the way these moves are done will you still be able to create 
you git history fixer script?

I imagine so - git doesn't actually track renames explicitly, so all that needs 
to be the case is that some git repo (or repos) exists with history from before 
the gitpocalypse, and some repo needs to exist with history after. If that's 
the case, we just set up a graft, and git will show them as moved files when 
you ask it to with --follow, -M, etc.

I imagine the graft file will look something like:
{code}
<first commit in combined repo trunk> <last commit in mr trunk> <last commit in 
hdfs trunk> <last commit in common trunk}
<first commit in combined 22> <last mr 22> <last hdfs 22> <last common 22>
...
{code}

This will make the first commit in the new branch a three-way merge of the 
other branches when looking at history.


(is there anything git can't do? I dont think so)

> Re-organize hadoop subversion layout
> ------------------------------------
>
>                 Key: HADOOP-7106
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7106
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>            Reporter: Nigel Daley
>            Assignee: Nigel Daley
>            Priority: Blocker
>             Fix For: 0.22.0
>
>         Attachments: HADOOP-7106.sh, HADOOP-7106.sh, HADOOP-7106.sh
>
>
> As discussed on general@ at http://tinyurl.com/4q6lhxm

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

        

Reply via email to