You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: TomH [Added to the original trac issue at 11.01pm, Friday, 3rd December 2010]
As best I can tell this is a bug in trac and therefore outside our control. The only limits we have configured are 100 files or 100000 bytes. Those are in place to prevent problems caused by large changesets taking a long time to render.
Author: TomH [Added to the original trac issue at 11.15pm, Friday, 3rd December 2010]
Apparently max_diff_bytes doesn't work the way any sane person would expect - it doesn't limit the size of the diff but rather the size of the files being diffed.
The total size of the files in that commit was more than 100Kb hence the diff wasn't shown.
I've removed that limit for now since we have a robots file blocking spiders from browsing the changsesets now anyway.
Reporter: sebastiank
[Submitted to the original trac issue database at 12.53pm, Friday, 3rd December 2010]
When displaying a changeset, trac can show a unified diff, like this:
http://trac.openstreetmap.org/changeset/24552
however this does not work, when more than 1 file has been touched
http://trac.openstreetmap.org/changeset/24567
It would be handy, if it showed the diff for each changeset
max_diff_bytes
andmax_diff_files
might be relevant settings.The text was updated successfully, but these errors were encountered: