From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH 1/2] test/dump-restore: new tests for empty files and leading comments/whitespace.
Date: Sun, 06 Jan 2013 22:53:05 -0400 [thread overview]
Message-ID: <87obh1r9f2.fsf@zancas.localnet> (raw)
In-Reply-To: <1356550593-21683-1-git-send-email-david@tethera.net>
david@tethera.net writes:
> From: David Bremner <bremner@debian.org>
>
> Three of these are marked broken; the third is a regression test,
> since it passes by virtue of batch-tag being the default input format.
pushed, with v2 of 2/2.
d
prev parent reply other threads:[~2013-01-07 2:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 19:36 [PATCH 1/2] test/dump-restore: new tests for empty files and leading comments/whitespace david
2012-12-26 19:36 ` [PATCH 2/2] notmuch-restore: handle empty input file, leading blank lines and comments david
2013-01-05 22:11 ` Tomi Ollila
2013-01-06 14:04 ` [Patch v2] " david
2013-01-06 15:28 ` Tomi Ollila
2013-01-07 2:53 ` 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=87obh1r9f2.fsf@zancas.localnet \
--to=david@tethera.net \
--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).