From: Tomi Ollila <tomi.ollila@iki.fi>
To: Gaute Hope <eg@gaute.vetsj.com>, notmuch <notmuch@notmuchmail.org>
Subject: Re: doc: notmuch_result_move_to_next -> notmuch_tags_move_to_next
Date: Sun, 09 Feb 2014 13:50:58 +0200 [thread overview]
Message-ID: <m28utkzeql.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <1391943009-sup-9107@qwerzila>
On Sun, Feb 09 2014, Gaute Hope <eg@gaute.vetsj.com> wrote:
> Greetings,
>
> another small typo in the docs. Patch attached.
the same typo seems to be in bindings/go/src/notmuch/notmuch.go too
(used git grep notmuch_result_move_to_next ...)
>
> Cheers, Gaute
Tomi
next prev parent reply other threads:[~2014-02-09 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 10:50 doc: notmuch_result_move_to_next -> notmuch_tags_move_to_next Gaute Hope
2014-02-09 11:50 ` Tomi Ollila [this message]
2014-02-13 12:46 ` 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=m28utkzeql.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=eg@gaute.vetsj.com \
--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).