From: David Bremner <david@tethera.net>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH 3/3] lib: clean up _notmuch_database_split_path
Date: Tue, 12 Apr 2016 20:51:00 -0300 [thread overview]
Message-ID: <87mvoy5qu3.fsf@zancas.localnet> (raw)
In-Reply-To: <1460317403-13714-3-git-send-email-jani@nikula.org>
Jani Nikula <jani@nikula.org> writes:
> Make the logic it a bit easier to read. No functional changes.
> ---
I decided to push all three patches; it wasn't clear Tomi reviewed all
3, but I had a look at the third. So, uh, if it's broken OH LOOK OVER
THERE ->
d
prev parent reply other threads:[~2016-04-12 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 19:43 [PATCH 1/3] test: test one character long directory names at top level Jani Nikula
2016-04-10 19:43 ` [PATCH 2/3] lib: fix handling of " Jani Nikula
2016-04-11 6:44 ` Tomi Ollila
2016-04-10 19:43 ` [PATCH 3/3] lib: clean up _notmuch_database_split_path Jani Nikula
2016-04-12 23:51 ` 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=87mvoy5qu3.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).