From: Jonathan Corbet <corbet@lwn.net>
To: git@vger.kernel.org
Subject: Announcing nntpgit
Date: Fri, 24 Feb 2012 13:39:42 -0700 [thread overview]
Message-ID: <20120224133942.49a7a420@dt> (raw)
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.
Be warned that this is very early stage software! It does what I need it
to do and little else. I've not tested it with any newsreaders other than
gnus, so the chances of interoperability problems with others are
significant. I'd be happy to accept bug reports, though, and even happier
to take patches. I hope it's useful to somebody.
jon
next reply other threads:[~2012-02-24 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 20:39 Jonathan Corbet [this message]
2012-02-24 21:38 ` Announcing nntpgit Junio C Hamano
2012-02-24 21:43 ` Jonathan Corbet
2012-02-27 21:02 ` Michael Haggerty
2012-02-25 0:58 ` Andreas Schwab
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=20120224133942.49a7a420@dt \
--to=corbet@lwn.net \
--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).