public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Kazutoshi Satoda <k_satoda@f2•dion.ne.jp>
To: "Torsten Bögershausen" <tboegi@web•de>,
	"Eric Wong" <normalperson@yhbt•net>
Cc: git@vger•kernel.org
Subject: Re: [PATCH 1/1] t9115: Skip pathnameencoding=cp932 under HFS
Date: Fri, 18 Mar 2016 11:14:34 +0900	[thread overview]
Message-ID: <56EB648A.2050802@f2.dion.ne.jp> (raw)
In-Reply-To: <56EA3DBD.2070105@web.de>

On 2016/03/17 14:16 +0900, Torsten Bögershausen wrote:
> On 2016-03-16 18.37, Kazutoshi Satoda wrote:
>> "funcky" looks a typo.
>> 
>>>>     Don't use funky file names, that can not be created under
>>>>     HFS or NTFS.
>> 
>> The file can be created on my Cygnus environment, which is under FONTS.
>> So it looks a bit inaccurate.

Uh, ... I noticed that I wrongly instruct the spell checker...

The above was meant to be:

  The file can be created on my Cygwin environment, which is under NTFS.
  So it looks a bit inaccurate.

>>>> -       neq=$(printf "\201\202") &&
>>>> -       git config svn.pathnameencoding cp932 &&
>>>> +       neq=$(printf "\303\244") &&
>>>> +       git config svn.pathnameencoding ISO8859-1 &&
>> 
>> The variable name "new" was for "NOT EQUAL TO" (0x8182 in cp932 = U+2260).
>> http://unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP932.TXT

Here "new" was meant to be "neq", of course.


Sorry for the confusion.

-- 
k_satoda

      parent reply	other threads:[~2016-03-18  2:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 15:19 [PATCH 0/2] enable "svn.pathnameencoding" on dcommit Kazutoshi Satoda
2016-02-08 15:20 ` [PATCH 1/2] git-svn: " Kazutoshi Satoda
2016-02-15  0:30   ` Eric Wong
2016-02-08 15:21 ` [PATCH 2/2] git-svn: apply "svn.pathnameencoding" before URL encoding Kazutoshi Satoda
2016-02-15  0:33   ` Eric Wong
2016-02-08 22:58 ` [PATCH 0/2] enable "svn.pathnameencoding" on dcommit Eric Wong
2016-02-15  0:52   ` [PULL] svn pathnameencoding for git svn dcommit Eric Wong
2016-02-15 21:32     ` Junio C Hamano
2016-02-16  3:29     ` Kazutoshi Satoda
2016-02-16  6:33       ` Eric Wong
2016-02-16 16:19         ` Kazutoshi Satoda
2016-02-20 23:37           ` Eric Wong
2016-02-21 13:12             ` Kazutoshi Satoda
2016-02-27 18:28   ` [PATCH 1/1] t9115: Skip pathnameencoding=cp932 under HFS tboegi
2016-02-28  4:59     ` Eric Wong
2016-02-28 17:52       ` Torsten Bögershausen
2016-03-15  1:59         ` Eric Wong
2016-03-15  5:23           ` Torsten Bögershausen
2016-03-15  7:09             ` Eric Wong
2016-03-16 17:37               ` Kazutoshi Satoda
2016-03-17  5:16                 ` Torsten Bögershausen
2016-03-17  5:35                   ` Torsten Bögershausen
2016-03-18  2:15                     ` Kazutoshi Satoda
2016-03-19  6:59                       ` Torsten Bögershausen
2016-03-18  2:14                   ` Kazutoshi Satoda [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56EB648A.2050802@f2.dion.ne.jp \
    --to=k_satoda@f2$(echo .)dion.ne.jp \
    --cc=git@vger$(echo .)kernel.org \
    --cc=normalperson@yhbt$(echo .)net \
    --cc=tboegi@web$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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