One other question (for now). I just did a ticket search for FileField, and I found a few tickets (#5655, #5619 in particular) that seem to be legitimate beefs, but their patches rely on pre-#5361 code. Should I consider #5361 to be on par with Malcolm's (many) refactors and try to roll fixes for these into #5361 and close them out in one commit? Or should I just leave them alone until #5361 goes in, then go back and add new patches based on the new code?
If I am to look at these all at once, would it be best for me to add a keyword (say, "filestorage") to these tickets to keep track of them better? Some of them (#4339, #5966 especially) might not get fixed directly, but if I tagged those as well, I'd be more likely to go back and explain how to achieve the desired effect with the new code. I just don't feel comfortable going beyond the scope of the current ticket without some acknowledgment that it's the right thing to do. -Gul --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
