From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Advertise per branch RSS/Atom feeds
Date: Sat, 11 Aug 2007 21:57:31 +0200 [thread overview]
Message-ID: <200708112157.31764.jnareb@gmail.com> (raw)
In-Reply-To: <7vps1ummqy.fsf@assigned-by-dhcp.cox.net>
On Sat, 11 August 2007, Junio C Hamano wrote:
> The feeder code had provisions to accept 'h' parameter to
> specify which branch to send the feed data from, but there was
> no link that advertised this capability on the pages.
>
> This adds h parameter to the footer of shortlog/log page for the
> branch.
And also of 'history' and 'tree' views; see comments below.
Besides, that is only half of the places where we put links to
RSS/Atom feeds. There are RSS/Atom feeds in the page header,
in the form of "<link .../>" elements; but that is perhaps for
separate patch. I think for example that we should add more
specialized feeds to HTML header instead of replacing generic
feeds by specialized ones like this patch does in footer.
> if (defined $project) {
> my $descr = git_get_project_description($project);
> + my @tips = ();
> + if ($hash !~ /^[0-9a-fA-F]{40}$/) {
> + @tips = (hash => $hash);
> + }
I'd use hash instead of array (list) here, c.f. %hash_base trick,
i.e. "my %tips" and "%tips = (hash => $hash);". Just for code
consistency and slightly better readibility.
By the way, the above would work also for 'history' and 'tree'
views if h parameter is not literal hash (perhaps we should exclude
"HEAD" as well, by the way), and we can have path limited feeds,
then perhaps it would be even better to use
%tips = (hash=>$hash, file_name=>$file_name);
I'm also not sure if %tips (or @tips) is best name for this variable,
but I don't have better proposal. %narrow perhaps or something like
that.
> if (defined $descr) {
> print "<div class=\"page_footer_text\">" . esc_html($descr) . "</div>\n";
> }
> - print $cgi->a({-href => href(action=>"rss"),
> + print $cgi->a({-href => href(action=>"rss", @tips),
> -class => "rss_logo"}, "RSS") . " ";
> - print $cgi->a({-href => href(action=>"atom"),
> + print $cgi->a({-href => href(action=>"atom", @tips),
> -class => "rss_logo"}, "Atom") . "\n";
> } else {
> print $cgi->a({-href => href(project=>undef, action=>"opml"),
>
And perhaps we should add title attribute explaining that feed is for
given branch... or perhaps not.
--
Jakub Narebski
Poland
prev parent reply other threads:[~2007-08-11 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 9:41 [PATCH] Advertise per branch RSS/Atom feeds Junio C Hamano
2007-08-11 19:57 ` Jakub Narebski [this message]
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=200708112157.31764.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@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).