On Tue, Feb 03, 2015 at 10:32:45AM +0100, Lukas Fleischer wrote:
> On Tue, 03 Feb 2015 at 10:17:15, Mike Hommey wrote:
> > Symptoms: $ git blame HEAD -- foo fatal: no such path foo in > garbage>
> >
> > Expected output: $ git blame HEAD -- foo fatal: no such path foo in
> > HEAD
> >
> > Bisect s
On Tue, 03 Feb 2015 at 10:17:15, Mike Hommey wrote:
> Symptoms:
> $ git blame HEAD -- foo
> fatal: no such path foo in
>
> Expected output:
> $ git blame HEAD -- foo
> fatal: no such path foo in HEAD
>
> Bisect says this was introduced in 1da1e07c835e900337714cfad6c32a8dc0b36ac3
> [...]
Symptoms:
$ git blame HEAD -- foo
fatal: no such path foo in
Expected output:
$ git blame HEAD -- foo
fatal: no such path foo in HEAD
Bisect says this was introduced in 1da1e07c835e900337714cfad6c32a8dc0b36ac3
valgrind output looks like this:
==4738== Memcheck, a memory error detector
=
3 matches
Mail list logo