From: Thomas Schwinge <thomas@schwinge.name>
To: Carl Worth <cworth@cworth.org>, Ali Polatel <alip@exherbo.org>,
notmuch@notmuchmail.org
Subject: Re: [ANN] notmuch-deliver
Date: Tue, 11 Jan 2011 12:46:38 +0100 [thread overview]
Message-ID: <87fwszacip.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <87pqufn1qh.fsf@yoom.home.cworth.org>
[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]
Hallo!
On Mon, 08 Nov 2010 09:50:46 -0800, Carl Worth <cworth@cworth.org> wrote:
> On Wed, 26 May 2010 17:01:34 +0300, Ali Polatel <alip@exherbo.org> wrote:
> > notmuch-deliver is a maildir delivery tool for notmuch mail indexer. It
> > reads from standard input, delivers the mail to the specified maildir
> > and adds it to the notmuch database. This is meant as a convenient
> > alternative to running notmuch new after mail delivery.
>
> Thanks for sharing this, Ali.
>
> What's the best way to advertise this to potential users?
I recently put a description and link onto the notmuch web pages.
> Should we include a separate utils directory in the notmuch repository
> with auxiliary programs like this?
I wouldn't do so. But that is not a very strong opinion of mine.
In general, I like it if I see a repository containing one specific tool,
and that one cleanly interfaces through specified interfaces with another
tool. These two things are no longer as cleanly visible once
notmuch-deliver was part of the notmuch repository.
> Or should we implement this functionality within the notmuch binary
> itself?
That's another option, of course. (And a separate discussion.)
> I'm open to suggestions.
>
> If nothing else, the notmuchmail.org web page should grow a section to
> point to auxiliary programs like this that users might find helpful.
I'm working on that (and other parts of the web pages) as I go on with
exploring the ``notmuch world''.
I'll also take the liberty to put stuff from the mailing list or IRC
discussions into web pages, for we have to document this notmuch beast
;-), and it's better to have a generic place to refer people to, instead
of discussing the same things more than once.
If someone disagrees with any of this, I'm open to discuss these items.
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2011-01-11 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 14:01 [ANN] notmuch-deliver Ali Polatel
2010-11-08 17:50 ` Carl Worth
2010-11-08 22:26 ` Ali Polatel
2011-01-11 11:46 ` Thomas Schwinge [this message]
2011-01-28 20:48 ` Carl Worth
2011-01-11 14:01 ` Felipe Contreras
2011-01-28 20:51 ` Carl Worth
2011-01-12 20:50 ` Austin Clements
2011-01-28 20:55 ` Carl Worth
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=87fwszacip.fsf@kepler.schwinge.homeip.net \
--to=thomas@schwinge.name \
--cc=alip@exherbo.org \
--cc=cworth@cworth.org \
--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).