Alexander Wuerstlein wrote:
There are 2 resolutions for this problem, changing the charset the webserver
delivers in the response headers or recoding the html to be utf-8. One
possibility to fix the response headers would be to use the 'AddDefaultCharset'
directive (http://httpd.apache.org/docs/2.2/de/mod/core.html#adddefaultcharset)
like 'AddDefaultCharset Off' or 'AddDefaultCharset ISO-8859-1'.
This could also be set in .htaccess, so the persons responsible for the subtree
can control the charset by themselves without your interaction. Of course
the right solution depends on your setup which you know best about :)
We're aware of this problem, and the first answer is the right one --
this is 2007 and UTF-8 is what we should use everywhere.
However, the second option (using .htaccess) is available.
-hpa
Oops, what happened to
http://git.kernel.org/?p=git/git.git;a=summary
(same for the kernel, btw)?
The main git.kernel.org page loads about half-way (without any stated
errors, but it's definitely broken and not complete), but the summary
pages don't seem to load at all (some projects do, but git and kernel
don't - it looks like the *cache* may still be working, but anything new
gets a "500 Internal Server Error").
Linus
On Sun, 22 Jul 2007, Linus Torvalds wrote:
The main git.kernel.org page loads about half-way (without any stated
errors, but it's definitely broken and not complete), but the summary
pages don't seem to load at all (some projects do, but git and kernel
don't - it looks like the *cache* may still be working, but anything new
gets a "500 Internal Server Error").
Ok, retried immediately after sending the email, and it's ok now. So never
mind - I probably tested just when some update was in progress..
Linus
Linus Torvalds wrote:
On Sun, 22 Jul 2007, Linus Torvalds wrote:
quoted
The main git.kernel.org page loads about half-way (without any stated
errors, but it's definitely broken and not complete), but the summary
pages don't seem to load at all (some projects do, but git and kernel
don't - it looks like the *cache* may still be working, but anything new
gets a "500 Internal Server Error").
Ok, retried immediately after sending the email, and it's ok now. So never
mind - I probably tested just when some update was in progress..
No, it ran out of disk space; I just cleaned it out.
-hpa