RE: [External] Re: gitk -m ?

From: Burkhardt, Glenn B UTAS <glenn.burkhardt@utas.utc.com>
Date: Aug 14, 2017, 13:20 UTC
Message-ID: <605cecc7f196495fa3d25113f28915e0@UUSALE0M.utcmail.com>
In-Reply-To: <7F03EAEF-DFDA-4CD0-86A1-A06C775A895B@madiva.com>

They don't.  In particular, information about commits that are parts of merges is missing.

Here's an example.  There are only two entries listed in 'gitk --all' for a particular file (sorry, I'd prefer to include a screen sho, but the mailing list doesn't allow HTML messages).

gitk --all MANIFEST.MF

Parent: f7462684ae78720aac05c929256d770118cf01fa (initial clone from Clearcase integ3 branch)
Branches: master, remotes/origin/master, remotes/origin/ww, ww
Follows: 
Precedes:

    require java 1.8

Child:  240f151d61fd4fd06f377bc52970b3574e5f9031 (require java 1.8)
Branches: master, remotes/origin/master, remotes/origin/ww, ww
Follows: 
Precedes:

    initial clone from Clearcase integ3 branch

git log with '-m' and '-follow' shows:

$ git log -m --follow --oneline MANIFEST.MF 9cc8be4 (from 1222d7c) Merge branch 'master' into ww; strategy "ours" a423f2d (from f869950) merge from ww branch; remove Bundle-NativeCode 51f0628 (from 2c6478c) Merge branch 'ww' of coverity:rmps into ww 240f151 require java 1.8 f746268 initial clone from Clearcase integ3 branch

-----Original Message-----
From: Uxío Prego [mailto:uprego@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 enough information.

Show 5 quoted lines

> On 3 Aug 2017, at 19:37, Burkhardt, Glenn B UTAS <Glenn.Burkhardt@utas.utc.com> wrote:
> 
> 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 request.
> 
> Thanks.