summaryrefslogtreecommitdiff
path: root/gitweb
diff options
context:
space:
mode:
authorGiuseppe Bilotta <giuseppe.bilotta@gmail.com>2009-01-26 12:50:14 +0100
committerJunio C Hamano <gitster@pobox.com>2009-01-28 14:13:54 -0800
commit0cf31285a0e1a40745eb2a91534f6e6b54df0e2f (patch)
treee7449882af41cfd5da908d4884e04395d9f04ea3 /gitweb
parent3ac109ae4c513b12959f3661b9d8f86b99f150d0 (diff)
downloadgit-0cf31285a0e1a40745eb2a91534f6e6b54df0e2f.tar.gz
gitweb: rss channel date
The RSS 2.0 specifications defines not one but _two_ dates for its channel element! Woohoo! Luckily, it seems that consensus seems to be that if both are present they should be equal, except for some very obscure and discouraged cases. Since lastBuildDate would make more sense for us and pubDate seems to be the most commonly used, we defined both and make them equal. Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'gitweb')
-rwxr-xr-xgitweb/gitweb.perl4
1 files changed, 4 insertions, 0 deletions
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index cc6d0fb79e..756868a7f9 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -6087,6 +6087,10 @@ XML
"<link>$alt_url</link>\n" .
"</image>\n";
}
+ if (%latest_date) {
+ print "<pubDate>$latest_date{'rfc2822'}</pubDate>\n";
+ print "<lastBuildDate>$latest_date{'rfc2822'}</lastBuildDate>\n";
+ }
print "<generator>gitweb v.$version/$git_version</generator>\n";
} elsif ($format eq 'atom') {
print <<XML;