From: David Bremner <david@tethera.net>
To: Stephen J Eglen <sje30@cam.ac.uk>, notmuch@notmuchmail.org
Subject: Re: Tags in the headers of mail files
In-Reply-To: <m1fr368ru8.fsf@sje30.cam>
References: <m1mrxf8mkt.fsf@sje30.cam> <87pl2bxjpu.fsf@tethera.net>
 <m1fr368ru8.fsf@sje30.cam>
Date: Tue, 02 Jun 2026 08:34:52 +0900
Message-ID: <87h5nlygv7.fsf@tethera.net>
MIME-Version: 1.0
Message-ID-Hash: GMSVJECXRXWJ2PORYD36BISUDJE6WENG
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Stephen J Eglen <sje30@cam.ac.uk> writes:

> That sounds very interesting David.  Where can I learn more about the git-remote-notmuch code?
>
> Best wishes,
>

You'll need a checkout of branch master from

       git clone https://git.notmuchmail.org/git/notmuch

The code is a bit indirect, as it's working via git-fast-export protocol
rather than creating files directly. Hopefully you can at least decode
the naming conventions and path encoding from there. There is also
documentation in docs/man1/git-remote-notmuch.rst, which is short enough
to reproduce here:

    Inside the prefix directory, there is a directory corresponding to
    each message-id in the notmuch database. The path of this directory is
    obtained by taking the first two bytes of the SHA1 hash of the
    message-id, followed by the hex escaped (in the manner documented in
    :any:`notmuch-dump(1)`) message name. For example, the message-id ``discourse/post/15986@community.mnt.re`` corresponds to directory::

          _notmuch_metadata/ae/27/discourse%2fpost%2f15986@community.mnt.re

    Inside each such directory is a (possibly empty) file containing the tags for that message, one per line.

Missing detail, the file is called "tags".
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org