From: "Torsten Bögershausen" <tboegi@web.de>
To: "Lars Schneider" <larsxschneider@gmail.com>,
"Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org, luke@diamand.org, gitster@pobox.com
Subject: Re: [PATCH v3] git-p4: add "--path-encoding" option
Date: Tue, 1 Sep 2015 16:35:04 +0200 [thread overview]
Message-ID: <55E5B798.40108@web.de> (raw)
In-Reply-To: <6BD3F017-37E4-4677-BCCE-D84E7031B780@gmail.com>
On 2015-09-01 14.47, Lars Schneider wrote:
>>> +test_expect_success 'Create a repo containing iso8859-1 encoded paths' '
>>> >> + cd "$cli" &&
>>> >> +
>>> >> + ISO8859="$(printf "$UTF8_ESCAPED" | iconv -f utf-8 -t iso8859-1)" &&
>>> >> + >"$ISO8859" &&
>>> >> + p4 add "$ISO8859" &&
>>> >> + p4 submit -d "test commit"
>>> >> +'
>> > Sorry for being persistant,
>> > but you can't create files with names that are ISO-8859-1 encoded under Mac OS,
>> > we end up like this:
>> >
>> > a-%E4_o-%F6_u-%FC.txt
> You are right. However, my goal is not to create a file with ISO-8859-1 characters in Mac OS. My goal is to create this file in Perforce and this approach seems to work.
>
>> >
But this line creates a file, doesn't it ?
>"$ISO8859" &&
(I just wonder how this works on you machine )
And, may be, we could fill the file with some content, to be double-sure that
the file name conversion works with Perforce ?
like
echo content >"$ISO8859" &&
and test the content later ?
next prev parent reply other threads:[~2015-09-01 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 22:10 [PATCH v3] git-p4: add "--path-encoding" option larsxschneider
2015-08-31 22:10 ` larsxschneider
2015-08-31 23:13 ` Junio C Hamano
2015-09-01 13:42 ` Lars Schneider
2015-09-01 17:19 ` Junio C Hamano
2015-09-01 17:35 ` Junio C Hamano
2015-09-01 18:55 ` Lars Schneider
2015-09-01 19:06 ` Junio C Hamano
2015-09-01 4:37 ` Torsten Bögershausen
2015-09-01 7:14 ` Fwd: " Torsten Bögershausen
2015-09-01 12:47 ` Lars Schneider
2015-09-01 14:35 ` Torsten Bögershausen [this message]
2015-09-01 15:02 ` Lars Schneider
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=55E5B798.40108@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
--cc=luke@diamand.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.
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).