From: Alex Riesen <raa.lkml@gmail.com>
Date: Fri, 01 Jun 2007 23:18:16 GMT
Subject: Re: [mingw port] git plumbing piping with CR/NL
Message-ID: <20070601231816.GC6360@steel.home>
In-Reply-To: <fcaeb9bf0706011123ue4ceaf2i12569c63d1d92584@mail.gmail.com>

Nguyen Thai Ngoc Duy, Fri, Jun 01, 2007 20:23:24 +0200:
> Hi,
> 
> I haven't had time looking at the code yet. I report here so that I
> can free my memory for other things. I made a command like this:
> 
> $ git ls-tree -r HEAD|grep blah.cc|git update-index --index-info
> 
> and the output of git-status was:
> 
> $ git status
> # On branch master
> # Changes to be committed:
> #   (use "git reset HEAD <file>..." to unstage)
> #
> #	new file:   path/to/blah.cc\r
> #
> # Changed but not updated:
> #   (use "git add/rm <file>..." to update what will be committed)
> #
> #	deleted:    path/to/blah.cc\r
> ...
> $ git version
> git version 1.5.2.651.g80e39-dirty (if the commit isn't in the master
> branch, it is based on master branch)
> 
> Apparently git should ignore \r at the end of the path. ...

Why should it? \r is a valid character in filenames almost everywhere
(except for the some proprietary OSes, as usual).

Why does your grep _alters_ the input, instead of filtering it, btw?