From: larsh at hjemli.net (larsh at hjemli.net)
Subject: [PATCH v2 RESEND 2/2] tests: properly quote arguments to printf
Date: Sun, 18 Mar 2012 10:57:07 +0000 [thread overview]
Message-ID: <20120318105707.GB15839@hjemli.net> (raw)
In-Reply-To: <1332067430-14837-2-git-send-email-mailings@hupie.com>
On Sun, Mar 18, 2012 at 11:43:50AM +0100, Ferry Huberts wrote:
> From: Ferry Huberts <ferry.huberts at pelagic.nl>
>
> v2: incorporate remarks of Lukas
Thanks, applied to stable.
--
larsh
next prev parent reply other threads:[~2012-03-18 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 10:43 [PATCH v2 RESEND 1/2] tests: handle paths with whitespace mailings
2012-03-18 10:43 ` [PATCH v2 RESEND 2/2] tests: properly quote arguments to printf mailings
2012-03-18 10:57 ` larsh [this message]
2012-03-18 10:56 ` [PATCH v2 RESEND 1/2] tests: handle paths with whitespace larsh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120318105707.GB15839@hjemli.net \
--to=cgit@lists.zx2c4.com \
/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.
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 NNTP newsgroup(s).