On Thu, Aug 13, 2009 at 4:08 PM, Peter2108 <pe...@monicol.co.uk> wrote:
> > I just ran into bug #6138 which is two years old now. There is a patch > supplied but it has not made it into the version I am using (1.1 rc1, > 11,332). Is there anyway to tell the Django Trace to notify me by > email when this bug is updated? > Since you've commented on the ticket, you'll automatically get mail when anyone updates the ticket. The other way to ensure you get updates in email is to add yourself to the cc list. As for why the patch has not been checked in -- the person who supplied the patch subsequently marked the ticket as "patch needs improvement" noting that the patch addressed only one aspect of the reported problem. Since then no one has supplied a complete patch. If you'd like to see the problem fixed, contributing a complete path would make the ticket more likely to move along in the process. I also don't see any tests in the existing patch, nor any reason why they wouldn't be necessary, so that is another thing a complete patch would likely need to include before the fix made it into the code base. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
