Ok, never mind. I had to log in first.....
On Thursday, February 18, 2016 at 11:20:19 AM UTC-6, Malik Rumi wrote: > > Thanks, but, that link goes to http://goog_1605940378/ and reports: > > The server at *goog_1605940378* can't be found, because the DNS lookup > failed. DNS is the network service that translates a website's name to its > Internet address. This error is most often caused by having no connection > to the Internet or a misconfigured network. It can also be caused by an > unresponsive DNS server or a firewall preventing Google Chrome from > accessing the network. > > I tried typing it in by hand, but then it redirected to > https://docs.djangoproject.com/en/1.9/ > > > > On Thursday, February 18, 2016 at 10:58:25 AM UTC-6, Tim Graham wrote: >> >> Please read https://code.djangoproject.com/newticket >> <http://goog_1605940378> for an explanation of what type of issue should >> be reported where. >> >> On Thursday, February 18, 2016 at 10:41:54 AM UTC-5, Malik Rumi wrote: >>> >>> Does it matter if a bug is reported to one and not the other? Is there >>> any difference between the two? Do the issue tracking numbers between the >>> two line up? >>> >> -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/fa3dea41-a9cf-4106-98c2-9bdac89ed74a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
