> Stefan Küng wrote:
>> Since this fix required quite a lot of changes to trunk code (which
>> isn't in 1.6.x), merging this to the stable branch won't work. I'd have
>> to manually fix this on the stable branch again - the code is just too
>> different there.
>> That's why I most likely just keep the fix on trunk and keep the bug on
> Thank you for the clarification. Sorry to bug you again, but just to be
> clear, does that mean I should not expect the fix to be in an official
> release until 1.7.0?
> For that matter, are all of the bugs/enhancements (BUG/CHG/NEW) in the
> Changelog.txt that ships with TSVN that are listed above the upcoming
> release (in this case 1.6.7) targeted for the next major release (1.7.0 in
> this case I presume) ... or is that just a holding bin for changes are yet
> to be targeted for any release?
Those are the changes that are scheduled for 1.7.0.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net