changeset.entries populated incorrectly in bootstrap from other than INITIAL revision

[anonymous]

If you bootstrap from some revision other than INITIAL (or r1 for svn source, or such), then your hook will be called with changeset.entries showing which files were touched in this revision. This is the wrong value for bootstrap -- your hook wants to process all files that are touched in the first revision in the target, if you see what I mean, not just all files that are touched in the bootstrap revision in the source.

[anonymous]

http://progetti.arstecnica.it/tailor/ticket/22

Is a hook which recursively processes every single (source code) file in the repository after every commit since it cannot rely on tailor to give it a complete changeset.entries every time. (Namely, tailor doesn't give it a complete set the first time.)

If tailor informed the hook that this was an initial commit, then the hook could do the full recursive operation that time, and then just process the changeset.entries files on all subsequent commits.

[lele]

Is some sort of a flag enough for your need? Or should tailor expand all the tree that is being imported?

[zooko@…]

Hm. Does this bug effect normal tailor processing as well as hooks? I am trying to tailorize Python SVN into darcs, starting from r2160, and I keep getting empty darcs repos with no contents. I wonder if it is because r2160 didn't add any files? Hm. No, because a bunch of files were added by r2161, so tailor should have picked them all up there.