unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "W. Trevor King" <wking@tremily.us>
To: David Bremner <bremner@debian.org>
Cc: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH] NEWS: Document "nmbug: Translate to Python"
Date: Tue, 7 Oct 2014 09:55:35 -0700	[thread overview]
Message-ID: <20141007165535.GC17059@odin.tremily.us> (raw)
In-Reply-To: <87k34c75o5.fsf@maritornes.cs.unb.ca>

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]

On Tue, Oct 07, 2014 at 08:30:34AM +0200, David Bremner wrote:
> W. Trevor King writes:
> > This is mostly culled from the commit message for 7f2cb3be (nmbug:
> > Translate to Python, 2014-10-03).  I realized while writing it
> > that the 7f2cb3be commit message has:
> 
> This seems a bit long for a NEWS item, especially for a change that
> impacts only a minority of current notmuch users. Typically even
> fairly major changes (from a user point of view) have less a 10-20
> line NEWS item and refer to some external documentation.

Ok, so maybe:

  “'nmbug help' is now 'nmbug --help', and the following nmbug
  commands have slightly different interfaces: 'archive', 'commit',
  'fetch', 'log', 'pull', 'push', and 'status'.  For details on the
  new interface, run 'nmbug COMMAND --help'.”

Cheers,
Trevor

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information,
see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-10-07 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-05 15:47 [PATCH] NEWS: Document "nmbug: Translate to Python" W. Trevor King
2014-10-07  6:30 ` David Bremner
2014-10-07 16:55   ` W. Trevor King [this message]
2014-10-07 17:10     ` David Bremner

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=20141007165535.GC17059@odin.tremily.us \
    --to=wking@tremily.us \
    --cc=bremner@debian.org \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /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).