From: David Bremner <david@tethera.net>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: nmfirehose - a crude nmbug companion tool
Date: Sun, 18 Mar 2012 10:49:13 -0300 [thread overview]
Message-ID: <874ntmkoiu.fsf@zancas.localnet> (raw)
In-Reply-To: <87wr6sypi9.fsf@nikula.org>
On Sun, 11 Mar 2012 02:01:34 +0200, Jani Nikula <jani@nikula.org> wrote:
>
> Hi all -
>
> There was some talk on IRC about maintaining a development branch
> containing the "maybe ready" patches [1] to better expose them to
> real-life use before merging to master.
Hi Jani;
Thanks for writing this. At least I find it useful, so maybe we should
include it (or some variation) in contrib. Probably make nmbug a
subdirectory, and put both in there.
d
prev parent reply other threads:[~2012-03-18 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 0:01 nmfirehose - a crude nmbug companion tool Jani Nikula
2012-03-18 13:49 ` 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=874ntmkoiu.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=jani@nikula.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).