unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Sean Whitton <spwhitton@spwhitton.name>, notmuch@notmuchmail.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: [nongnu] main 385623dca6 2/2: * elpa-packages (notmuch): New package.
Date: Wed, 21 Dec 2022 07:53:13 -0400	[thread overview]
Message-ID: <87k02lrn12.fsf@tethera.net> (raw)
In-Reply-To: <871qot1w7e.fsf@melete.silentflame.com>

Sean Whitton <spwhitton@spwhitton.name> writes:

>
> I know that you don't want to commit notmuch-pkg.el to git, and that's
> in fact undesirable from a NonGNU ELPA point of view, it turns out.  But
> given how there is already version.txt and version.py, could we have a
> header in notmuch.el too, do you think?

The existence of version.py is a bug that we hope to fix soon. It is
used only by the obsolete and deprecated python bindings. Current
bindings (under bindings/python-cffi) use version.txt.

Adding a version header to notmuch.el and maintaining it
semi-automatically in the way version.py is seems more fragile (sed'ing
a file also edited by humans) and more work (the code to generate
notmuch-pkg.el already exists).

  parent reply	other threads:[~2022-12-21 11:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167139941586.12438.1105626110857907494@vcs2.savannah.gnu.org>
     [not found] ` <20221218213656.56E0AC0061B@vcs2.savannah.gnu.org>
     [not found]   ` <jwvv8m551h4.fsf-monnier+emacs@gnu.org>
2022-12-20 23:39     ` [nongnu] main 385623dca6 2/2: * elpa-packages (notmuch): New package Sean Whitton
2022-12-21  5:07       ` Stefan Monnier
2022-12-21 12:30         ` David Bremner
2022-12-21 11:53       ` David Bremner [this message]
2022-12-22 20:54         ` Sean Whitton

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=87k02lrn12.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=notmuch@notmuchmail.org \
    --cc=spwhitton@spwhitton.name \
    /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).