"Yngve Nysaeter Pettersen" <yngve@xxxxxxxxx> writes: > The split command will create a new repository for all files foo in a > folder (path/foo) and their commit history. > > The replant command reverses that process, re-adding the path prefix > for each file. It may be possible to extend that process into one that > automatically reintegrates the new commits in the original history, > but I never had time to complete that work. > > I did originally add the "replant" functionality into my version of > the git-subtree script, but given the number of commits in the > original repository, git-subtree turned out to be inefficient, due to > the use of temporary files (tens of thousands of files IIRC). > > Those problems led to my development of git-splitter in Python > (bypassing the problem of temporary files), but just including the > functionality I needed, join was not one of those functions. That still doesn't answer the question: why did you need to write a new tool instead of extending git-subtree? If one doesn't use "replant", is your tool different from git-subtree? -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html