(sorry if this is a double post, we switched our ISP this morning, and
as I didn't see the mail go through, I'm reposting)
Emmanuel Blot wrote:
>> I'll second this. I don't want Trac coalescing changesets.
>>
>
> So do I.
> I'm not sure whether this feature can be useful, but if it is
> implemented and kept, it should be optional and *not* be enabled in
> the default settings.
Well, have you checked what the feature does precisely?
I don't see what harm it can do: only strictly consecutive changesets,
having the same author and same message are replaced by a "Changesets
[from:to]" entry, which saves space, but doesn't loose any information
(except you get only the time for the last changeset in the sequence).
You can get to the full information ("expand" the list, as Waldemar
suggested) simply by clicking on the link, which takes you to the
corresponding log view for that revision range. From there, you have a
quick way to grasp the whole span of changes at once, by using the view
differences button, or you can go to the individual changes.
I'm OK to make it optional for those not wanting that feature, but I
don't see any good reason to turn it /off/ by default.
-- Christian
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
