Julian Phillips wrote: > At some point in the "messy" phase I get an error from fast-import saying: > > fatal: path foo not in branch > > This seems to happen when I attempt to copy a file that is also changed in > the same commit. What I would like to do is find out what things look > like just before that point - the problem is that fast-import seems to not > create anything on failure. So, apart restarting the import and stopping > just before the broken commit, is there any way to find out what > fast-import thinks the branch looks like? Redirect the input stream to a file instead of to fast-import, then feed fast-import from this file. This way you can reproduce the failure more quickly. Also, you can run fast-import from a debugger. -- Hannes - 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
