Mike Hommey wrote:
>> These edits are numerous and spread over many months, so the typical
>> history fixup-sessions involve periods where you make 30 random
>> historicaledits per hour (which need to be viewed and checked every time
>> immediately after making the change). And say once every 4 months, you
>> run it through git filter-branch to cast everything into stone. A
>> typical git filter-branch run takes 15 minutes on a repository this
>> size.
>I think the point was more about making a tool to do exactly what you
>want, based on the new git sequencer. Note that git filter-branch could
>also be rewritten to use the sequencer.
As far as I understood it, the new git sequencer rewrites history
proper. That is timeconsuming by definition, and thus it is *not*
possible to make a tool based on the sequencer that supports the desired
iterative-history-rewrite workflow.
--
Sincerely,
Stephen R. van den Berg.
You are confused; but this is your normal state.
--
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
