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

Re: Announcing nntpgit

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Feb 27, 2012, 21:02 UTC
Message-ID
<4F4BEF67.1070609@alum.mit.edu>
In-Reply-To
<7v62evykrq.fsf@alter.siamese.dyndns.org>
On 02/24/2012 10:38 PM, Junio C Hamano wrote:
Show 11 quoted lines
> 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?
>From contrib/hooks/post-receive-email I've locally derived a Python

version that sends one email message per commit. It generates a thread of messages for each reference that was pushed, starting with a summary of how the reference was changed, and one followup email for each new commit added to that reference. In a threaded mail reader, this groups all of the changes to a reference due to a particular push in a thread that can easily be expanded, collapsed, or deleted as a group. I find this a convenient workflow.

I believe that NNTP threading works much the same way as email threading, so probably the same style could be used there. My script is still not published, though.

Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Previous: Jonathan CorbetNext: Andreas Schwab
Message 4 of 5 in “Announcing nntpgit”
  1. Jonathan CorbetFeb 24, 2012
  2. Junio C HamanoFeb 24, 2012
  3. Jonathan CorbetFeb 24, 2012
  4. Michael HaggertyFeb 27, 2012
  5. Andreas SchwabFeb 25, 2012

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.