From: Ricky Zhou <ricky@fedoraproject.org>
To: Mike Hommey <mh@glandium.org>
Cc: Todd Zullinger <tmz@pobox.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jakub Narebski <jnareb@gmail.com>
Subject: Re: [PATCH] Use   instead of for XHTML compliance
Date: Wed, 15 Apr 2009 12:38:29 -0400 [thread overview]
Message-ID: <20090415163829.GD3316@sphe.res.cmu.edu> (raw)
In-Reply-To: <20090415155013.GA15518@glandium.org>
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
On 2009-04-15 05:50:14 PM, Mike Hommey wrote:
> is very much xhtml compliant, so the problem must lie somewhere
> else, possibly in privoxy.
Sorry for the noise, I've confirmed that this only happens with
torbutton is used.
Thanks,
Ricky
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-15 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 15:40 [PATCH] Use   instead of for XHTML compliance Todd Zullinger
2009-04-15 15:50 ` Mike Hommey
2009-04-15 16:38 ` Ricky Zhou [this message]
2009-04-15 15:55 ` Jakub Narebski
2009-04-15 16:21 ` Ricky Zhou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090415163829.GD3316@sphe.res.cmu.edu \
--to=ricky@fedoraproject.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=mh@glandium.org \
--cc=tmz@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).