On Monday 19 February 2007, Manuzhai wrote: > > Hello all, > > I'd like to discuss two recent changesets with which I don't necessarily agree. > > The first is r4769 [1], which fixes issue #3421 [2]. This patch > visually merges two or more consecutive changesets when the author and > commit messages are the same, but I'm not sure this is a good idea. In > my opinion, the timeline is important in that it serves as a good > overview of what's been happening to a project, but with this patch, > information on changesets can is conflated. Of course, having many > commits with a similar/the same message is in most cases just a Bad > Idea, and I don't like how Trac codifies that this is okay. Also, with > the current code this is not a preference, so I can't easily turn this > behavior off.
I'll second this. I don't want Trac coalescing changesets. Eli --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
