From: Jonathan Corbet <corbet@lwn.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Announcing nntpgit
Date: Fri, 24 Feb 2012 14:43:09 -0700 [thread overview]
Message-ID: <20120224144309.4657052e@dt> (raw)
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:
> 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
next prev parent reply other threads:[~2012-02-24 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 20:39 Announcing nntpgit Jonathan Corbet
2012-02-24 21:38 ` Junio C Hamano
2012-02-24 21:43 ` Jonathan Corbet [this message]
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=20120224144309.4657052e@dt \
--to=corbet@lwn.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).