On Wed, Nov 21, 2018 at 02:54:34PM +0100, Marc Gonzalez wrote:
> If I specify the branch to explore, git grep prints a colon instead of
> a slash in the path:
>
> $ git grep arm,coresight-tmc master:Documentation/devicetree
> master:Documentation/devicetree:bindings/arm/coresight.txt:
> "arm,coresight-tmc", "arm,primecell";
> master:Documentation/devicetree:bindings/arm/coresight.txt:
> compatible = "arm,coresight-tmc", "arm,primecell";
>^
> HERE
>
> There is no such issue when the branch is not specified:
>
> $ git grep arm,coresight-tmc Documentation/devicetree
> Documentation/devicetree/bindings/arm/coresight.txt:
> "arm,coresight-tmc", "arm,primecell";
> Documentation/devicetree/bindings/arm/coresight.txt:compatible =
> "arm,coresight-tmc", "arm,primecell";
> ^
> NO ISSUE
>
>
> Is this expected behavior?
> The spurious colon prevents one from simply copy/pasting the output.
There's lots of discussion in this thread from last year:
https://public-inbox.org/git/20170119150347.3484-1-stefa...@redhat.com/
Notably:
git grep arm,coresight-tmc master -- Documentation/devicetree
will do what you want.
-Peff