At Fri, 24 May 2013 03:26:45 -0400, Eli Barzilay wrote: > If that can be done reliabely, then of course it makes it possible to > do the split reliabley after the first restructure.
Great! Let's do that, because I remain convinced that it's going to be a lot easier. > * Also, I'd worry about file movements on top of paths that existed > under a different final path at some point I believe the file-lifetime computation in "slice.rkt" takes care of that. > * The script should also take care to deal with files that got removed > in the past. Ditto. > * Actually, given the huge amount of time it's running (see next > bullet), it's probably best to make it do the movements from all > paths at the same time. There's no need to move anything while extracting a repository slice; the movements happen before. > * It's not clear to me what you want to do at this point, [...] > Alternatively, do the first restructure with in-repo moves instead, Yes, that's what I suggested. _________________________ Racket Developers list: http://lists.racket-lang.org/dev
