On Mon, Jul 15, 2013 at 3:21 PM, Sean Woods <s...@seanwoods.com> wrote: > >> This all works fine, with one significant exception. When I do a >> diff operation on many files that are updated during the incremental >> import, it appears that the entire file is "new." In other words, >> the left hand side of the diff is blank and the right hand side is >> entirely green. If I do a unified diff, the entire screen is green. >> I look at the patch, and it's filed with plus signs. Etc. > > Just wondering if anyone else had ideas about this issue. Perhaps I'm > not interpreting the meaning of "incremental" properly? I checked the > src/import.c code in the fossil repository but will need to do a > little more digging to really understand what's going on (need to > study up on fossil repository structure, etc). > > Any guidance or impressions would be greatly appreciated.
I've been patching the import code on my little spare time and, from what I've seen, I'm under the impression that incremental import is not supported. So, I believe that the "--incremental" option of the import command is a bit misleading. The only thing it does is to open an existing SQLite database without complaining. The problem with incremental imports is the SHA1 hash mapping between git and Fossil: in the pure content case (blobs) they may be the same, but the correspondence between git commits and manifest artifacts is not currently saved anywhere. I don't think it should be too much difficult to do though, because every other version control system does it. If you have some patience, I may take a look at it once I finish testing my import patches that generate delta manifests. Regards. -- Isaac Jurado "The noblest pleasure is the joy of understanding" Leonardo da Vinci _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
