Re: Announcing nntpgit

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 24, 2012, 21:38 UTC
Message-ID: <7v62evykrq.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20120224133942.49a7a420@dt>

Jonathan Corbet <corbet@lwn.net> writes:

Show 22 quoted lines

> When kernel.org went down, it took the mainline kernel commits list with
> it. That had a fairly serious and unfortunate effect on my workflow,
> which, among other things, depends on knowing what's being merged.  I
> hacked up various workarounds, but none of them were as useful or
> efficient.
>
> Eventually it occurred to me that what I *really* wanted was the commit
> stream as an NNTP feed so I could read it in gnus along with most of the
> other lists I follow.  The result was nntpgit, a small Python3 program
> that tracks repository branches and makes new commits available as
> "articles" to all comers.  I've been working with it for a few weeks now
> and I'm quite happy; it works better for me than the old list did.
>
> Should anybody wish to experiment with it, they can do so in two ways.
> First, the code is available (GPLv2) from:
>
> 	git://git.lwn.net/nntpgit.git
>
> Alternatively, it's running on port 8119 on git.lwn.net.  There are
> currently two "newsgroups": lwn.mainline for mainline commits, and
> lwn.networking for davem's networking tree.  I expect to add others over
> time.

Neat.

This is something I wanted to write (or see somebody write so that I can use it ;-)) even before I became the maintainer of this project, as I practically live inside GNUS, but never got around to go beyond the design phase.

How do you handle message threading (References: and In-Reply-To:)?

Would a commit on the "mainline" (a rough approximation of it would be "log --first-parent" starting from the tip) form the discussion starter article, and any side branch that fork from them would be a discussion thread starting at the commit?