From: Kevin Locke <kevin@kevinlocke.name>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Subject: Re: [Request] gitweb: tag feeds
Date: Sat, 17 Oct 2020 07:46:55 -0600 [thread overview]
Message-ID: <20201017134655.GA127715@kevinlocke.name> (raw)
In-Reply-To: <xmqqtuuuceat.fsf@gitster.c.googlers.com>
On Fri, 2020-10-16 at 09:43 -0700, Junio C Hamano wrote:
> Kevin Locke <kevin@kevinlocke.name> writes:
>> I've found the support for Atom and RSS commit feeds in gitweb to be
>> very useful. I'd like to extend the support to include tag feeds as a
>> simple means of announcing/tracking releases. Might such a feature be
>> acceptable in some form?
>>
>> Giuseppe Bilotta raised this idea and provided an implementation in
>> 2012[1] and 2017[2] which did not receive any responses on-list that I
>> could find. Would these be a suitable starting point?
>
> I suspect that these patches would have been OK back then.
>
> The thing is, it appears nobody actively maintains gitweb anymore,
> which cuts both ways.
>
> - We may not have made fundamental changes to the program in the
> last 3 years, so patches from 2017 may still be relevant.
>
> - Even if 2017 patch were to be resurrected, nobody would be able
> to review and vouch for the result.
>
> So, if you still use gitweb and want to take over its maintenance,
> or if we can revive interest in those who want to maintain it,
> perhaps.
Understandable. Thanks for explaining the situation! That's good to
know.
For my current needs, switching to another web interface, like cgit,
seems preferable.
Best,
Kevin
prev parent reply other threads:[~2020-10-17 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 22:12 [Request] gitweb: tag feeds Kevin Locke
2020-10-16 16:43 ` Junio C Hamano
2020-10-17 13:46 ` Kevin Locke [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201017134655.GA127715@kevinlocke.name \
--to=kevin@kevinlocke.name \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=giuseppe.bilotta@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).