From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCHv2 3/6] gitweb: rss feed managingEditor
Date: Fri, 6 Feb 2009 12:03:26 +0100 [thread overview]
Message-ID: <cb7bb73a0902060303s35527b3ey8572d60c54066e33@mail.gmail.com> (raw)
In-Reply-To: <200902050019.44016.jnareb@gmail.com>
On Thu, Feb 5, 2009 at 12:19 AM, Jakub Narebski <jnareb@gmail.com> wrote:
> On Mon, 26 Jan 2009, Giuseppe Bilotta wrote:
>
>> The RSS 2.0 specification allows an optional managingEditor tag for the
>> channel, containing the "email address for person responsible for editorial
>> content", which is basically the project owner.
>
> Hmmm... does it make sense with gitweb? Perhaps it does...
I must confess I had my own doubts about this 8-D
>> Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
>> ---
>> gitweb/gitweb.perl | 4 +++-
>> 1 files changed, 3 insertions(+), 1 deletions(-)
>>
>> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
>> index 3d94f50..cc6d0fb 100755
>> --- a/gitweb/gitweb.perl
>> +++ b/gitweb/gitweb.perl
>> @@ -6074,7 +6074,9 @@ XML
>> print "<title>$title</title>\n" .
>> "<link>$alt_url</link>\n" .
>> "<description>$descr</description>\n" .
>> - "<language>en</language>\n";
>> + "<language>en</language>\n" .
>> + # project owner is responsible for 'editorial' content
>> + "<managingEditor>$owner</managingEditor>\n";
>
> Shouldn't we esc_html($owner), just in case it is for example
> "O Wner <owner@example.com>" (either via gitweb.owner or via
> projects_index being text file listing projects, because I don't
> see GECOS having email in it...)?
>
Indeed, itt's probably safer to do the escaping.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2009-02-06 11:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 11:50 [PATCHv2 0/6] gitweb: feed metadata enhancements Giuseppe Bilotta
2009-01-26 11:50 ` [PATCHv2 1/6] gitweb: channel image in rss feed Giuseppe Bilotta
2009-01-26 11:50 ` [PATCHv2 2/6] gitweb: feed generator metadata Giuseppe Bilotta
2009-01-26 11:50 ` [PATCHv2 3/6] gitweb: rss feed managingEditor Giuseppe Bilotta
2009-01-26 11:50 ` [PATCHv2 4/6] gitweb: rss channel date Giuseppe Bilotta
2009-01-26 11:50 ` [PATCHv2 5/6] gitweb: last-modified time should be commiter, not author Giuseppe Bilotta
2009-01-26 11:50 ` [PATCHv2 6/6] gitweb: check if-modified-since for feeds Giuseppe Bilotta
2009-02-05 2:03 ` Jakub Narebski
2009-02-06 11:19 ` Giuseppe Bilotta
2009-02-04 23:38 ` [PATCHv2 5/6] gitweb: last-modified time should be commiter, not author Jakub Narebski
2009-02-06 11:14 ` Giuseppe Bilotta
2009-02-06 21:12 ` Jakub Narebski
2009-02-06 23:00 ` Giuseppe Bilotta
2009-02-11 3:10 ` Deskin Miller
2009-02-11 9:02 ` Giuseppe Bilotta
2009-02-11 9:18 ` Jakub Narebski
2009-02-11 9:54 ` Giuseppe Bilotta
2009-02-12 4:50 ` Deskin Miller
2009-02-12 9:07 ` Jakub Narebski
2009-02-12 9:52 ` Giuseppe Bilotta
2009-02-12 10:11 ` Jakub Narebski
2009-02-12 11:23 ` Giuseppe Bilotta
2009-02-04 23:24 ` [PATCHv2 4/6] gitweb: rss channel date Jakub Narebski
2009-02-06 11:10 ` Giuseppe Bilotta
2009-02-04 23:19 ` [PATCHv2 3/6] gitweb: rss feed managingEditor Jakub Narebski
2009-02-06 11:03 ` Giuseppe Bilotta [this message]
2009-02-04 23:15 ` [PATCHv2 2/6] gitweb: feed generator metadata Jakub Narebski
2009-02-06 11:01 ` Giuseppe Bilotta
2009-02-06 11:21 ` Jakub Narebski
2009-02-04 22:56 ` [PATCHv2 1/6] gitweb: channel image in rss feed Jakub Narebski
2009-02-06 10:55 ` Giuseppe Bilotta
2009-01-28 20:58 ` [PATCHv2 0/6] gitweb: feed metadata enhancements Junio C Hamano
2009-01-28 21:48 ` Jakub Narebski
2009-01-28 21:57 ` Giuseppe Bilotta
2009-01-28 22:03 ` Junio C Hamano
2009-02-06 22:42 ` Jakub Narebski
2009-02-07 0:24 ` Junio C Hamano
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=cb7bb73a0902060303s35527b3ey8572d60c54066e33@mail.gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.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).