git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] gitweb: Add hash parameter in feed URL when a hash is specified in the current request

From
JQJean-Baptiste Quenot <jbq@caraldi.com>
Date
Mar 21, 2008, 19:14 UTC
Message-ID
<ae63f8b50803211214i59184fd7jde7d640d6a8580b8@mail.gmail.com>
In-Reply-To
<m3skyjvrgr.fsf@localhost.localdomain>

I just read your initial post, and IMHO we should keep it simple. I tested the various links, and it appears to be good-enough to pass the hash parameter for all URLs that do not specify the hash parameter explicitly. You can still pass it on a per-link basis if you think it's too simplistic.

Maybe it's not the perfect solution, but at least it will improve the current situation where some people are apparently deceived by not having a per-branch RSS feed. Not everyone forges URLs like we do :D

Oh, and about the title, just appending the hash is sufficient. What's important is the contents of the feed. Users will probably end up editing the feed title in their reader after all.

Cheers,
-- 
Jean-Baptiste Quenot
http://caraldi.com/jbq/blog/
Previous: Jakub NarebskiNext: Jakub Narebski
Message 3 of 4 in “gitweb: Add hash parameter in feed URL when a hash is specified in the current request”
  1. gitweb: Add hash parameter in feed URL when a hash is specified in the current requestJean-Baptiste Quenot, Mar 21, 2008
  2. Jakub NarebskiMar 21, 2008
  3. Jean-Baptiste QuenotMar 21, 2008
  4. Jakub NarebskiMar 21, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.