From: Jakub Narebski <jnareb@gmail.com>
To: hanwen@xs4all.nl
Cc: git@vger.kernel.org
Subject: Re: tracking separate branches with RSS
Date: Tue, 14 Nov 2006 03:21:58 +0100 [thread overview]
Message-ID: <200611140321.58749.jnareb@gmail.com> (raw)
In-Reply-To: <455920EC.7060804@xs4all.nl>
Han-Wen Nienhuys wrote;
> 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
prev parent reply other threads:[~2006-11-14 2:21 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
2006-11-14 1:50 ` Han-Wen Nienhuys
2006-11-14 2:21 ` 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=200611140321.58749.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/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).