{"thread":{"id":"12039","subject":"[RFC] gitweb: Use feed link according to current view","startedAt":"2008-02-11T18:00:12Z","lastAt":"2008-02-11T18:00:12Z","messageCount":1,"participants":["Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"68414","messageId":"200802111900.12325.jnareb@gmail.com","threadId":"12039","inReplyTo":null,"subject":"[RFC] gitweb: Use feed link according to current view","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-02-11T18:00:12Z","receivedAt":"2008-02-11T18:00:12Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Michael G. Noll said in comments to the \"Switching my code repository\nfrom Subversion (SVN) to git\" article (http://tinyurl.com/37v67l) in\nhis \"My digital moleskine\" blog, that one of the things he is missing\nin gitweb from SVN::Web is an RSS feed with news/information of the\ncurrent view (including RSS feed for single file or directory).\n\nThis is not exactly true, as since refactoring feed generation in\n  \"gitweb: Refactor feed generation, make output prettier,\n   add Atom  feed\"\n  commit-af6feeb229110a0fa77a179c2655fca08e72f879\ngitweb can generate feeds (RSS or Atom) for history of a given branch,\nhistory limited to a given directory, or history of a given file.\nNevertheless this required handcrafting the URL to get wanted RSS\nfeed.\n\n\nThe question is what feeds should be shown, both in <link .../> in page \nheader, and in [Atom][RSS] links at the bottom of the page. Some things \nare fairly obvious:\n * projects list page has OPML feed (I'm open to suggestions for better\n   format) with list of feeds, one \"'summary' page\" feed per project\n * 'summary' page has feed(s) starting from HEAD (default: no arguments)\n * 'tree' view should have link to feed of a history of a directory\n * 'blob' and 'blame' views should have link to feed of a history\n    of file\n * 'log' and 'shortlog' views should have feed from a given commit\n * 'history' view should have link to feed of a history of pathspec\n\nSome things needs some considerations:\n * should 'commit' and 'commitdiff' views have feed of log\n   starting from given commit (positive commit in the case of diff)?\n * should 'treediff' and 'blobdiff' have feed of history of given\n   directory or a file, starting from the 'to' version?\n\nFor some views it is hard to find a feed:\n * for 'forks' view we could have OPML feed limited to forks\n   of a projects, like for projects list page\n * for 'heads' and 'tags' we could have OPML of log feeds for\n   branches and tags\n * Should for 'tag' view if it points to a commit, have feed\n   like for 'commit' view?\n * What should be (if there should be any) feed for 'search'\n   page?\n\nAnd there are also pesky details. Should we offer in HTML <head> also\nno-merges and first-parent (and no-merges + first-parent) versions\nof feeds? Should we offer also follow version of a history of a file\nfeed? For example for 'blob' view should we also offer full log feed,\nnot only limited to given path? Should we always offer full feed\nstaring from HEAD (default feed)?\n\nThanks in advance for comments and answers.\n-- \nJakub Narebski\nPoland\n"}]}