git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Brian Gernhardt <benji@silverinsanity.com>, git@vger.kernel.org
Subject: Re: [PATCH] Use "-f" when adding files with odd names in t9200.
Date: Sat, 3 Feb 2007 22:47:22 -0500	[thread overview]
Message-ID: <20070204034722.GA16766@spearce.org> (raw)
In-Reply-To: <7vr6t6zq2d.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <junkio@cox.net> wrote:
> This is not to make any point but purely for my own education,
> but I wonder what would happen on HFS+ to the following
> sequence, which does not involve any git operation:
> 
> Doesn't the grep fail to find the file that was successfully
> created in the previous step?

Indeed.  I stole the path "gitweb/test/M\303\244rchen" from git.git
and ran your script on Mac OS X:

  $ cat jt.sh; echo; sh jt.sh 
  #!/bin/sh
  LANG=C LC_ALL=C
  export LANG LC_ALL
  
  rm -fr testrepo
  mkdir testrepo
  cd testrepo
  
  pathname='Märchen'
  echo $pathname
  echo hello >"$pathname"
  /bin/ls | fgrep -e "$pathname" | wc -l
  
  pathname='Mrchen'
  echo $pathname
  echo hello >"$pathname"
  /bin/ls | fgrep -e "$pathname" | wc -l
  Märchen
         0
  Mrchen
         1

The first pathname= line in the above script is the *exact* byte
sequence which appears in gitweb/test's tree.  I apologize if my
email chain screws up the line.

-- 
Shawn.

  reply	other threads:[~2007-02-04  3:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-03 15:56 t9200 still failing Brian Gernhardt
2007-02-03 16:17 ` Wolfgang Fischer
2007-02-03 17:41   ` Brian Gernhardt
2007-02-03 18:13     ` [PATCH] Use "-f" when adding files with odd names in t9200 Brian Gernhardt
2007-02-03 19:42       ` Junio C Hamano
2007-02-03 20:12         ` Brian Gernhardt
2007-02-03 20:51           ` Junio C Hamano
2007-02-03 21:31             ` Brian Gernhardt
2007-02-03 23:50               ` Junio C Hamano
2007-02-04  1:09                 ` Junio C Hamano
2007-02-04  3:47                   ` Shawn O. Pearce [this message]
2007-02-04 16:35                 ` Brian Gernhardt
2007-02-04 16:50                   ` Brian Gernhardt
2007-02-05  1:30                     ` Junio C Hamano
2007-02-05  1:55                       ` Brian Gernhardt
2007-02-06 15:17                       ` Brian Gernhardt
     [not found]     ` <82643737-7D5F-4A73-83BA-EB5AD9BBA5EA@wf227.com>
2007-02-03 19:41       ` t9200 still failing Brian Gernhardt

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=20070204034722.GA16766@spearce.org \
    --to=spearce@spearce.org \
    --cc=benji@silverinsanity.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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).