Re: Change #2: Modify prototypes of replace_*() and add_*()

> 2. Do pass it to each replace_*() or add_*(), because although it's
> constant across the update right now, things might not always so.

Anything might not always be so, but that's not a priori a good reason
for excess baggage.

If updates start producing non-constant target revisions, then we'll
also have the problem of non-constant target revisions for files which
didn't change (and thus have no replace or add operation).
Received on Sat Oct 21 14:36:19 2006