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

Re: Announcing nntpgit

From
JCJonathan Corbet <corbet@lwn.net>
Date
Feb 24, 2012, 21:43 UTC
Message-ID
<20120224144309.4657052e@dt>
In-Reply-To
<7v62evykrq.fsf@alter.siamese.dyndns.org>

On Fri, 24 Feb 2012 13:38:33 -0800 Junio C Hamano <gitster@pobox.com> wrote:

Show 6 quoted lines
> 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?

There's really no threading at all at this point; it's just a linear series of commits-as-messages as provided by a vanilla "git log". I could certainly see trying to do something fancier, if it were useful, but it's not something I've thought about much yet.

Like I said, it's really young stuff :)
jon
Previous: Junio C HamanoNext: Michael Haggerty
Message 3 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.