Bug#415775: remove AddDefaultCharset in lenny?
I believe adding AddDefaultCharset was a bad idea. It is only to be used if one _knows_ that the files have that charset, which we definitely don't. It also overrides two out of three valid ways to specify the charset of a page: the meta tag and type maps (see #414429). Only the way via AddCharset remains functional. Now the question is: Should we reverse that for lenny and comment AddDefaultCharset out? signature.asc Description: This is a digitally signed message part.
Re: r392 - in /trunk/apache2: apache2-doc.conf changelog
[EMAIL PROTECTED] Log: Don't use AddDefaultCharset for our docs You know, I think I agree with those (including you, I notice, reading #415775 again) who say we shouldn't be using AddDefaultCharset _at all_. The issue came up a bit too late for etch, but I think for lenny it is reasonable to remove /etc/apache2/conf.d/charset and leave only the commented line in /etc/apache2/apache2.conf. signature.asc Description: Digital signature
Re: r392 - in /trunk/apache2: apache2-doc.conf changelog
On Dienstag, 26. Juni 2007, Peter Samuelson wrote: but I think for lenny it is reasonable to remove /etc/apache2/conf.d/charset and leave only the commented line in /etc/apache2/apache2.conf. ok. Maybe we can change that together with the change of /etc/default/apache2 to a conffile and the removal of NO_START. I have already started to work on that and was planning to include it in 2.2.4-2. I want to upload 2.2.4-1 as soon as 2.2.3-5 is in testing, which is still waiting for mpm-itk on sparc. signature.asc Description: This is a digitally signed message part.
[bts-link] source package apache2
# # bts-link upstream status pull for source package apache2 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #294648 # * http://issues.apache.org/bugzilla/show_bug.cgi?id=14090 # * remote status changed: (?) - NEW usertags 294648 + status-NEW thanks
[bts-link] source package apache2
# # bts-link upstream status pull for source package apache2 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #353443 # * http://issues.apache.org/bugzilla/show_bug.cgi?id=12355 # * remote status changed: REOPENED - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 353443 + fixed-upstream usertags 353443 - status-REOPENED usertags 353443 + status-RESOLVED resolution-FIXED thanks
