From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: [RFC] gitweb: Use feed link according to current view
Date: Mon, 11 Feb 2008 19:00:12 +0100 [thread overview]
Message-ID: <200802111900.12325.jnareb@gmail.com> (raw)
Michael G. Noll said in comments to the "Switching my code repository
from Subversion (SVN) to git" article (http://tinyurl.com/37v67l) in
his "My digital moleskine" blog, that one of the things he is missing
in gitweb from SVN::Web is an RSS feed with news/information of the
current view (including RSS feed for single file or directory).
This is not exactly true, as since refactoring feed generation in
"gitweb: Refactor feed generation, make output prettier,
add Atom feed"
commit-af6feeb229110a0fa77a179c2655fca08e72f879
gitweb can generate feeds (RSS or Atom) for history of a given branch,
history limited to a given directory, or history of a given file.
Nevertheless this required handcrafting the URL to get wanted RSS
feed.
The question is what feeds should be shown, both in <link .../> in page
header, and in [Atom][RSS] links at the bottom of the page. Some things
are fairly obvious:
* projects list page has OPML feed (I'm open to suggestions for better
format) with list of feeds, one "'summary' page" feed per project
* 'summary' page has feed(s) starting from HEAD (default: no arguments)
* 'tree' view should have link to feed of a history of a directory
* 'blob' and 'blame' views should have link to feed of a history
of file
* 'log' and 'shortlog' views should have feed from a given commit
* 'history' view should have link to feed of a history of pathspec
Some things needs some considerations:
* should 'commit' and 'commitdiff' views have feed of log
starting from given commit (positive commit in the case of diff)?
* should 'treediff' and 'blobdiff' have feed of history of given
directory or a file, starting from the 'to' version?
For some views it is hard to find a feed:
* for 'forks' view we could have OPML feed limited to forks
of a projects, like for projects list page
* for 'heads' and 'tags' we could have OPML of log feeds for
branches and tags
* Should for 'tag' view if it points to a commit, have feed
like for 'commit' view?
* What should be (if there should be any) feed for 'search'
page?
And there are also pesky details. Should we offer in HTML <head> also
no-merges and first-parent (and no-merges + first-parent) versions
of feeds? Should we offer also follow version of a history of a file
feed? For example for 'blob' view should we also offer full log feed,
not only limited to given path? Should we always offer full feed
staring from HEAD (default feed)?
Thanks in advance for comments and answers.
--
Jakub Narebski
Poland
reply other threads:[~2008-02-11 18:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200802111900.12325.jnareb@gmail.com \
--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).