unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: "W. Trevor King" <wking@tremily.us>
Cc: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: nmbug in the Debian packages?
Date: Sat, 13 Feb 2016 20:49:19 -0400	[thread overview]
Message-ID: <8737sw9kvk.fsf@zancas.localnet> (raw)
In-Reply-To: <20160213220250.GB4265@odin.tremily.us>

"W. Trevor King" <wking@tremily.us> writes:

> I'd floated notmuch-dtag earlier [1].  Does that sound right?  Or do
> folks prefer another name?

I'd like to hear feedback from others about that.

>> It would also need some tests.
>
> In tests/, or devel/dtag/tests?  If the latter, how should I handle
> the test framework?  Symlinks to the main tests/?  Copies?  Sharness
> submodule?  Other ideas?

in test/

>
> That seems like something that could be handled independently.  If
> folks want to set it up, adjusting the !command handler in notmuch.c's
> main() or adjusting find_command to fall back to “this is probably an
> external command” seem doable.
>
yeah, I guess there's no need to overcomplicate thing. But let's adopt a
git-style convention of "notmuch-foo" for script names, so we can make
it more transparent later, if needed.

  reply	other threads:[~2016-02-14  0:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06 18:24 nmbug in the Debian packages? David Edmondson
2016-02-06 19:24 ` Tomi Ollila
2016-02-06 19:25   ` David Edmondson
2016-02-06 21:15   ` David Bremner
2016-02-06 21:50     ` Tomi Ollila
2016-02-08 11:33 ` David Bremner
2016-02-08 11:39   ` David Edmondson
2016-02-08 19:38   ` W. Trevor King
2016-02-13 18:17     ` David Bremner
2016-02-13 22:02       ` W. Trevor King
2016-02-14  0:49         ` David Bremner [this message]
2016-02-16 13:16         ` David Bremner
2016-02-17 10:55           ` David Edmondson

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=8737sw9kvk.fsf@zancas.localnet \
    --to=david@tethera.net \
    --cc=dme@dme.org \
    --cc=notmuch@notmuchmail.org \
    --cc=wking@tremily.us \
    /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).