From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: git@vger.kernel.org
Subject: Re: tracking separate branches with RSS
Date: Tue, 14 Nov 2006 02:50:36 +0100 [thread overview]
Message-ID: <455920EC.7060804@xs4all.nl> (raw)
In-Reply-To: <ejb410$nvg$1@sea.gmane.org>
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.
> 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
next prev parent reply other threads:[~2006-11-14 1:56 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 [this message]
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=455920EC.7060804@xs4all.nl \
--to=hanwen@xs4all.nl \
--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).