On 6/1/07, Alex Riesen <raa.lkml@xxxxxxxxx> wrote:
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).
Right. Although I doubt usage of \r and other special characters in filenames.
Why does your grep _alters_ the input, instead of filtering it, btw?
I have no idea. It's grep from MKS Toolkit FYI. -- Duy - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
