the 'Enter files' section. The
> error message was:
>
> Can't parse git log output: {commit 9cc8be... faab99... }
>
> -Original Message-
> From: Uxío Prego [mailto:upr...@madiva.com]
> Sent: Monday, August 14, 2017 12:47
> To: Burkhardt, Glenn B
was:
Can't parse git log output: {commit 9cc8be... faab99... }
-Original Message-
From: Uxío Prego [mailto:upr...@madiva.com]
Sent: Monday, August 14, 2017 12:47
To: Burkhardt, Glenn B UTAS
Cc: git@vger.kernel.org
Subject: Re: [External] Re: gitk -m ?
I do not know if you ca
om: Uxío Prego [mailto:upr...@madiva.com]
Sent: Monday, August 14, 2017 01:12
To: Burkhardt, Glenn B UTAS
Cc: git@vger.kernel.org
Subject: [External] Re: gitk -m ?
Not sure what you are wanting to achieve, but please make sure neither
`gitk PATHSPEC` nor `gitk --all PATHSPEC` are presenting you eno
m: Uxío Prego [mailto:upr...@madiva.com]
Sent: Monday, August 14, 2017 01:12
To: Burkhardt, Glenn B UTAS
Cc: git@vger.kernel.org
Subject: [External] Re: gitk -m ?
Not sure what you are wanting to achieve, but please make sure neither `gitk
PATHSPEC` nor `gitk --all PATHSPEC` are presenting you e
Not sure what you are wanting to achieve, but please make sure neither `gitk
PATHSPEC` nor `gitk --all PATHSPEC` are presenting you enough information.
> On 3 Aug 2017, at 19:37, Burkhardt, Glenn B UTAS
> wrote:
>
> I've been looking in 'gitk' for an option that does what 'git log -m' does.
>
I've been looking in 'gitk' for an option that does what 'git log -m' does.
Did I miss something? In particular, I'd like to get information about a file
that's currently available with "git log -m --all --follow", but presented in
'gitk'. If it's not there, please consider this a feature req
6 matches
Mail list logo
