On 10/4/07, James Bennett <[EMAIL PROTECTED]> wrote: > > Just let it go already, and turn your time and attention to a real bug.
But see, it is a real bug, at least to people with a certain work style, and not one they can fix themselves by runnig their own patched django, since it's a "bug" with the official website. Personally I don't care one way or the other (it's not my work style), but I can appreciate the problem for some. It's a problem for Mikkel, he researched it, found someone had previously opened a ticket that was closed wontfix with an offhand-sounding "we don't really need one", and raised the issue here to see what others thought. More than a dozen piped up to agree they thougt a favicon a good idea, a few alternatives were posted, one of which seemed to get broad acceptance from those interested. And the response from anyone with the power to do anything was ..... silence. Nobody said it was a bad idea, or the icon was unacceptable, or it was too much work, or even reiterated that they still didn't think it was necessary even given the discussion. Personally it didn't strike me as antagonistic to have re-raised the issue. Indeed even after today's responses I'm left sitting here curious as to "whyever not?", and I don't even care if it happens. Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
