From: Sebastian Pipping <webmaster@hartwork.org>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: gitweb atom feeds broken (on repo.or.cz only?)
Date: Wed, 14 Oct 2009 16:35:17 +0200 [thread overview]
Message-ID: <4AD5E1A5.7020909@hartwork.org> (raw)
In-Reply-To: <20091014141744.GO6695@machine.or.cz>
Petr Baudis wrote:
> On Tue, Oct 13, 2009 at 02:14:48PM +0200, Sebastian Pipping wrote:
>> Petr, any news on this one?
>>
>> I just check and it still seems broken.
>
> Fixed, it's a HTML::Email::Obfuscate bug.
Though the feed works in Firefox now I wouldn't call it fixed, yet,
As I elaborated earlier in this thread the Atom you generate is not
valid. I cannot put it better than feedvalidator:
http://feedvalidator.org/check.cgi?url=http%3A%2F%2Frepo.or.cz%2Fw%2Fdottout.git%3Fa%3Datom
Please fix that, too.
Sebastian
next prev parent reply other threads:[~2009-10-14 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 17:35 gitweb atom feeds broken (on repo.or.cz only?) Sebastian Pipping
2009-09-28 7:23 ` Tay Ray Chuan
2009-09-28 14:44 ` Sebastian Pipping
2009-10-13 12:14 ` Sebastian Pipping
2009-10-14 14:17 ` Petr Baudis
2009-10-14 14:35 ` Sebastian Pipping [this message]
2009-10-14 14:40 ` Petr Baudis
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=4AD5E1A5.7020909@hartwork.org \
--to=webmaster@hartwork.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).