On Apr 11, 1:15 pm, Marc Fargas <teleni...@telenieko.com> wrote: > That's a but in TRAC's svn-commit-hook script, there's a ticket about it in > TRAC's TRAC with workarounds and so onhttp://trac.edgewall.org/ticket/3508.
Thanks. Actually reading through that ticket, it appears there is no bug in recent versions of Trac (less than 3 years old), if the proper version of the svn-commit-hook and all plugins are used (and PYTHON_EGG_CACHE writability issues aren't causing a problem). So it's not a matter of "workarounds" for a bug in Trac - it seems this should work if everything is set up correctly. > You can fill a ticket in Django asking for some workaround but you shouldn't > rely on those mails too much. There's no question of "relying" on them for some mission-critical purpose; it'd just be nice to get the notification, "most of the time" is fine. I'll file a ticket. Carl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
