From: David Bremner <david@tethera.net>
To: Ethan Glasser-Camp <ethan.glasser.camp@gmail.com>,
notmuch@notmuchmail.org
Cc: Ethan Glasser-Camp <ethan@betacantrips.com>
Subject: Re: [PATCH] test: handle filenames that have directories in them
Date: Thu, 18 Oct 2012 09:02:39 -0300 [thread overview]
Message-ID: <87r4owm1i8.fsf@zancas.localnet> (raw)
In-Reply-To: <1350074609-21769-1-git-send-email-ethan@betacantrips.com>
Ethan Glasser-Camp <ethan.glasser.camp@gmail.com> writes:
> Since $TEST_DIRECTORY is an absolute path, any filenames generated
> with it will be complete paths. Only use the basename to generate
> suffixes for filenames.
pushed.
d
prev parent reply other threads:[~2012-10-18 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 20:43 [PATCH] test: handle filenames that have directories in them Ethan Glasser-Camp
2012-10-18 5:43 ` Tomi Ollila
2012-10-18 12:02 ` 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=87r4owm1i8.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=ethan.glasser.camp@gmail.com \
--cc=ethan@betacantrips.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).