From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: tracking separate branches with RSS
Date: Tue, 14 Nov 2006 01:54:03 +0100 [thread overview]
Message-ID: <ejb410$nvg$1@sea.gmane.org> (raw)
In-Reply-To: ejb3hh$nvr$1@sea.gmane.org
Han-Wen Nienhuys wrote:
> I think that the shortlog / RSS support in gitweb is really neat.
> However, it seems to track only the master branch.
>
> In our repository (http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=summary),
> we track two completely disparate branches in one repository: we have
> both the project and the website for the project in branches
>
> master
>
> and
>
> web/master
>
> Unfortunately, I don't seem to get any updates in my RSS reader when I
> push something to web/master. Would it be possible have a separate feed
> for each branch? I tried looking at the gitweb script, but my perl-fu
> is too weak to figure out how to pass an argument from the URL into a
> git_rss() to replace the
>
> git_get_head_hash($project)
>
> call.
For quick'n'dirty solution it would be enough to just replace
git_get_head_hash($project)
with
$hash || "HEAD"
(or $hash || git_get_head_hash($project)).
Then to track branch 'branch' with RSS just use
?p=project.git;a=rss;h=branch
as a query string.
I started doing it, but the problem is that you have to change also a bit
of contents, for example summary/title, and some links.
git_rss subroutine is one of the few subroutines which didn't get refactored.
> A second possibility -less desirable, but better than nothing- is to
> have commits from all branches show up in the shortlog and the RSS feed.
Use "--all" as 'h' (hash) parameter.
P.S. What do you think about moving from RSS to Atom for feeds?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-11-14 0:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 0:44 tracking separate branches with RSS Han-Wen Nienhuys
2006-11-14 0:54 ` Jakub Narebski [this message]
2006-11-14 1:50 ` Han-Wen Nienhuys
2006-11-14 2:21 ` Jakub Narebski
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='ejb410$nvg$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).