From: Jakub Narebski <jnareb@gmail•com>
To: git@vger•kernel.org
Subject: Re: How to supply "raw" bytes to git grep?
Date: Thu, 18 Sep 2008 18:31:30 +0200 [thread overview]
Message-ID: <gatvp0$kl0$1@ger.gmane.org> (raw)
In-Reply-To: 200809181728.18597.johan@herland.net
Johan Herland wrote:
> I wanted to list all text files in my repo which contain carriage
> returns, so I tried the following command-line:
>
> git grep --cached -I -l -e <CR>
>
> where <CR> is some magic incantation that I've yet to figure out. I've
> tried all the obvious cases (\r, 0x0d, \015, etc.), but none of them
> seem to DWIM...
Why not use _literal_ CR; of course protecting it by piockung it by
shell as end of command by quites, for example
$ git grep --cached -I -l -e '
'
It works for me (bash).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2008-09-18 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 15:28 How to supply "raw" bytes to git grep? Johan Herland
2008-09-18 15:46 ` Jacob Helwig
2008-09-18 16:18 ` Johan Herland
2008-09-18 22:07 ` Kalle Olavi Niemitalo
2008-09-18 16:31 ` Jakub Narebski [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='gatvp0$kl0$1@ger.gmane.org' \
--to=jnareb@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/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