user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Threading in git repo?
Date: Wed, 13 Mar 2019 18:07:07 -0500	[thread overview]
Message-ID: <20190313230707.GB210027@google.com> (raw)

Hi Eric,

As far as I can tell, pi git repos have no branching: each new message
is added as a child commit of the most recent message, even if it is a
response to an older message.  Have you considered making the new
message a child of the message it is responding to?

I'm fiddling with making neomutt read a pi git repo.  Currently I only
read the git log info (not the commit bodies).  It's pretty fast to
read the author, date, and subject (since you conveniently stash them
in the commit metadata), but since I'm not reading the mail headers,
neomutt can't do all its threading magic.

It seems like working out the threading could be done once at the time
the message is added to the git repo, and threads could appear as
branches in the repo.

Bjorn

             reply	other threads:[~2019-03-13 23:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 23:07 Bjorn Helgaas [this message]
2019-03-14  7:44 ` Threading in git repo? Eric Wong
2019-03-18 21:38   ` Bjorn Helgaas
2019-03-18 23:04     ` Eric Wong

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190313230707.GB210027@google.com \
    --to=helgaas@kernel.org \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).