tigefa4u projects Trac

Wrap the changeset message log in the revision log text mode (a.k.a. the Changelog)

Actually, this would have been working since the start if I had used the appropriate template variable...

Fix for a minor bug whereby a new, empty custom field would appear with a ''deleted'' message on first ticket comment on existing tickets as it picked up a change from `None` to `''` (empty string).

Ticket and patch on #4447 by thatch.

Fixing some inconsistency in method signature for 2 interface methods - we don't use `self` anywhere else in Interface classes. As we don't check the method signatures, this is really just API documentation.

Closes #5657

Don't try to figure out the exact oldest rev in case of scoped Subversion revs.

We don't do that because it has apparently a big perfomance impact, and moreover is the trigger for a huge memory leak, as documented in #5213.

However, getting the exact start of a the history in a scoped repository was important for the resync, so we still have to do that at this occasion.

I keep the lines as comments instead of deleting them completely, as a reminder to investigate the reasons of that leak.

Closes #5213.

Don't try to display the frame information in the backtrace when a !MemoryError occurred.

Trying to render the frame data usually triggers ''another'' !MemoryError exception, hiding the potentially interesting backtrace of the first one, like in #4081 and #6101.

Follow-up to r6295: make the file revision string information global to the module.

Also enhances the plugins admin panel so that it can show that information.

Plugins admin panel: need to adapt the test for windows, where normcase has already been used (see #2329)

Standardize all text files on ''native'' eol-style. Fixes #5576

Follow-up to [6317] and #2876. First attempt caused new issues (#6490), and now the implementation has changed to use the existing API to update enums instead of writing new SQL.

Ticket ''Clone'' now simply pre-fills the new ticket form, and doesn't actually directly create the ticket, so one can still modify it, preview it before creating it (or not! if the button was pressed by mistake...)