| No comments on this?
It works for me. Shall I commit this fix, or are there potential issues with it?
On 10/11/2011, at 3:17 PM, Steve Bennett wrote: On 10/11/2011, at 2:50 PM, Steve Bennett wrote: On 10/11/2011, at 2:30 PM, Steve Bennett wrote: I tried to do something similar, using a git tag to keep track of where I was up to for the incremental import.
It mostly works, except the timeline shows each import as disconnected from the previous import. See attached.
For the import at 21:40, I tried to import one previous rev hoping that they would be merged, but this didn't happen. Is this "disconnect" fixable?
I guess the problem is that the first commit of an incremental import has no ancestor identified. Would it be possible to identify the ancestor somehow, either on the command line, or by finding the tip of the corresponding branch?
The attached patch works for my simple case of always importing to the tip of trunk, but I'm sure it is highly dubious in other situations.
-- WorkWare Systems Pty Ltd
|
import-incremental-ancestor.patch
Description: Binary data
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
