threads / discuss / 43361

Re: tracking separate branches with RSS

Subject: Re: tracking separate branches with RSS

## tl;dr

4 messages between Nov 14, 2006 and Nov 14, 2006.

replies: 3people: 2as markdown or json

Han-Wen Nienhuys· Nov 14, 2006, 00:44 UTC · lore

tracking separate branches with RSS

Hello,

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.

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.

-- 
  Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

Jakub Narebski· Nov 14, 2006, 00:54 UTC · re: Han-Wen Nienhuys · lore

Han-Wen Nienhuys wrote:

Show 22 quoted lines

> 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

Han-Wen Nienhuys· Nov 14, 2006, 01:50 UTC · re: Jakub Narebski · lore

Jakub Narebski escreveu:

Show 5 quoted lines

>> 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.
>

This doesn't seem to work. Note that I'm savannah.gnu.org, which may run an older version. The quickest way to get this up and running is to have real patches appear in the official release, and convince Sylvain to upgrade to a better gitweb.

> P.S. What do you think about moving from RSS to Atom for feeds?

I don't know: as far as I'm concerned, both are things that I paste into Thunderbird's "News & Blog" section, and then it magically works. (or doesn't, as in this case).

-- 
  Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

Jakub Narebski· Nov 14, 2006, 02:21 UTC · re: Han-Wen Nienhuys · lore

Han-Wen Nienhuys wrote;

Show 12 quoted lines

> Jakub Narebski escreveu:
> 
>>> 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.
>> 
> 
> This doesn't seem to work.  Note that I'm savannah.gnu.org, which may 
> run an older version. The quickest way to get this up and running is to 
> have real patches appear in the official release, and convince Sylvain 
> to upgrade to a better gitweb.

Sorry, I should have made more clear that it would work only _after_ mentioned changes.

-- 
Jakub Narebski