On Jun 24, 2009, at 8:54 AM, Remy Blank wrote:
> 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. Personally I still prefer svnmerge.py if nothing else because it generates the log messages nicely. Also svn merge is very messy and tends to little properties all over the codebase that get very annoying. --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
