Christian Boos wrote:
> One nice feature of the script vs. the command 
> was that with svnmerge you could explicitly record a change as being 
> "blocked", whereas with the command, you have to fake the merge (using 
> --record-only, as shown in r8297 above). But that's a minor thing.

It means that we lose information compared to the svnmerge.py script,
namely the revisions that we explicitly didn't want to merge. OTOH, the
most useful information given by the merge properties is the revisions
eligible for merging. I have never gone back in the repository history
to find out why a revision was blocked, so I don't mind.

I'll follow with the majority.

-- Remy


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to