From: Johannes Sixt <j.sixt@viscovery.net>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, James Gregory <j.gregory@epigenesys.co.uk>
Subject: Re: [PATCH] fast-export: quote paths in output
Date: Fri, 05 Aug 2011 13:12:06 +0200 [thread overview]
Message-ID: <4E3BD006.6010005@viscovery.net> (raw)
In-Reply-To: <20110805105526.GA22480@sigill.intra.peff.net>
Am 8/5/2011 12:55, schrieb Jeff King:
> +test_expect_success 'fast-export quotes pathnames' '
> + git init crazy-paths &&
> + (cd crazy-paths &&
> + >"$(printf "path with\\nnewline")" &&
> + >"path with \"quote\"" &&
> + >"path with \\backslash" &&
> + >"path with space" &&
Please construct the tree object using git-update-index's --cacheinfo or
--index-info rather than using actual files and git add so that the test
can pass on filesystems that do not allow newlines, quotes, or
backslashes(!) in filenames.
-- Hannes
--
"Atomic objects are neither active nor radioactive." --
Programming Languages -- C++, Final Committee Draft (Doc.N3092)
next prev parent reply other threads:[~2011-08-05 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 10:55 [PATCH] fast-export: quote paths in output Jeff King
2011-08-05 11:12 ` Johannes Sixt [this message]
2011-08-05 22:36 ` Jeff King
2011-08-05 22:55 ` Junio C Hamano
2011-08-06 2:36 ` Jeff King
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=4E3BD006.6010005@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.gregory@epigenesys.co.uk \
--cc=peff@peff.net \
/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).