unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: public-inbox, nmbug or Debbugs and notmuch sync?
Date: Mon, 09 May 2022 20:24:58 +0200	[thread overview]
Message-ID: <87bkw64l8l.fsf@gmail.com> (raw)
In-Reply-To: <87wneu20uz.fsf@tethera.net>

Hi David,

Thanks for the answer.

On Mon, 09 May 2022 at 12:15, David Bremner <david@tethera.net> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:

>>  2. Notmuch is strongly linked to the Maildir format as storage but Git
>>  seems an efficient way to exchange and sync across several machines; for
>>  instance using the tool grokmirror [4].  Does it make sense to have
>>  another backend for Notmuch than Maildir?
>
> I don't know grokmirror, it looks like a layer on top of git. You
> can commit maildir to git if you like, notmuch doesn't really care.
> As far as having a backend that is not just mail files on disk, that
> seems unlikely, but I guess you never know.

For instance, I have never been fully satisfied by a tool synchronizing
several large Maildir across machines.  Or a tool for mirroring a public
mailing list.  Unsatisfied because such tool are inefficient or long to
configure; except muchsync which is strongly focused on notmuch.

A tool as public-inbox makes that easy by relying on Git.  Maybe I
misunderstand but from my understanding public-inbox does not track the
files under Maildir as a whole using Git but store [1] the messages in the
Git history, one message per commit.  Somehow, only the last message is
plainly visible and all the others are “hidden” under .git/ as various
Git objects.

Note that in addition, public-inbox can be configured using Xapian.
Well, I am not interested by this part since Notmuch perfectly fits my
needs.

I like an unified interface – I am really happy with Emacs – and the
Emacs fronted for Notmuch.

Somehow, on one hand, I find really handy public-inbox (and other tools
as lei or b4) to follow various public mailing lists.  On the other
hand, I still have (private) email inboxes and I find really handy
Notmuch.  Even, I find really handy Emacs+Notmuch to read and filter all
the messages.

Therefore, I have to convert from public-inbox to maildir and then index
for reading or searching with Emacs+Notmuch.  Otherwise, I would have to
do the opposite and convert my maildirs sync with IMAP to public-inbox
format.

Somehow, I would like to have a bridge: keep Emacs+Notmuch but index
emails with another format (backend) than maildir as
public-inbox-v2-format.  It would avoid data duplication and/or
conversion.

1: <https://public-inbox.org/public-inbox-v2-format.html>


>>  3. Debian or GNU use instances of Debbugs.  Tools as ’mailscripts’ [5]
>>  using ’bts’ CLI [6] are great.  Personally, I prefer the Emacs packages
>>  ’piem’ [7] and ’debbugs’ [8].  Well, the point is to be able to inject
>>  the bug report to my local inboxes – for reading offline or for
>>  tagging.  How could I bridge the Debbugs meta info with a local ’nmbug’?
>
> You can use notmuch-slurp-debbug (from mailscripts) to get the mail
> messages. I haven't thought about synchronizing metadata with
> debbugs. In principle I guess it should be possible.

About notmuch-slurp-debbug, thanks.  I have tried it, but it uses the
Perl script ’bts’ and it is not packaged for Guix… Aside it would
require some tweaks, if I have checked correctly.

From my point of view, Debbugs is old and many things as interaction is
a poor experience.  The Guix community has a layer named Mumi [2] on the
top of the GNU instance of Debbugs.  You can find an instance here [3].
Well, another story. ;-)

Somehow, if ’nmbug’ would be able to extract the meta info from Debbugs,
roughly speaking a map between Message-ID and status, and this map would
be stored as Notmuch tags.  Then, using “notmuch git” would allow an
easy way for synchronizing my local copy of the bugs mailing lists with
the current state of Debbugs.  Bah, I do not know. ;-)


2: <https://git.elephly.net/?p=software/mumi.git;a=summary>
3: <https://issues.guix.gnu.org/>


Thanks again for the answer.

Cheers,
simon\r

  reply	other threads:[~2022-05-09 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 12:02 public-inbox, nmbug or Debbugs and notmuch sync? zimoun
2022-05-09 15:15 ` David Bremner
2022-05-09 18:24   ` zimoun [this message]
2022-05-09 19:07     ` David Bremner
2022-05-10  7:09       ` zimoun

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://notmuchmail.org/

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

  git send-email \
    --in-reply-to=87bkw64l8l.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).