From: David Bremner <david@tethera.net>
To: inwit <inwit@sindominio.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] doc: make post-new hook description more precise
Date: Fri, 11 Feb 2022 13:43:36 -0400 [thread overview]
Message-ID: <8735kpz4c7.fsf@tethera.net> (raw)
In-Reply-To: <20220211165632.1062266-1-inwit@sindominio.net>
inwit <inwit@sindominio.net> writes:
> Add the word "any" to the description of post-new hook description in order to clarify that it is always run, even if there are no new messages.
>
> _______________________________________________
> notmuch mailing list -- notmuch@notmuchmail.org
> To unsubscribe send an email to notmuch-leave@notmuchmail.org
Smashed these two messages together and applied to master.
d
prev parent reply other threads:[~2022-02-11 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 16:56 [PATCH] doc: make post-new hook description more precise inwit
2022-02-11 16:56 ` [PATCH] doc: make post-hook " inwit
2022-02-11 17:43 ` David Bremner [this message]
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=8735kpz4c7.fsf@tethera.net \
--to=david@tethera.net \
--cc=inwit@sindominio.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).