On Wed, May 22, 2013 at 8:21 PM, Matthew Flatt <mfl...@cs.utah.edu> wrote:
> At Wed, 22 May 2013 14:50:41 -0400, Eli Barzilay wrote: > > That's true, but the downside of changing the structure and having > > files and directories move post structure change will completely > > destroy the relevant edit history of the files, since it will not be > > carried over to the repos once it's split. > > It's possible that we're talking past each other due to me not getting > this point. > > Why is it not possible to carry over history? > > The history I want corresponds to `git log --follow' on each of the > files that end up in a repository. I'm pretty sure that such a history > of commits can be generated for any given set of files, even if no > ready-made tool exists already (i.e., 'git' is plenty flexible that I > can script it myself). > > Or maybe I'm missing some larger reason? > I was going to comment on the same thing. While a naive use of "git filter-branch" might not retain the history, it should be entirely possible to do something a little more intelligent and keep that history. Essentially each of the new repositories could keep the entire history of the original repository, followed by a massive move/rename, then moving forward with an individual package. --Carl
_________________________ Racket Developers list: http://lists.racket-lang.org/dev
