# "gitk --author=foo" shows also parent 4 messages from 2016-04-26 to 2016-04-26. Participants: Nikolai Kosjar, Mike Rappazzo, Jeff King. Thread: https://gitlist.dev/t/42148 ## Nikolai Kosjar, 2016-04-26 13:08 Subject: "gitk --author=foo" shows also parent Message-ID: <571F6852.1070405@qt.io> URL: https://gitlist.dev/e/571F6852.1070405%40qt.io ``` Hi! $ gitk --author=foo ...seems to show also the parent of each author-matched commit, whereas $ git log --author=foo does not. Is this intended or a bug? I've stumbled over this while configuring a gitk view with the author field. Nikolai # Setup ~/work/gitkBug % git init . ~/work/gitkBug % touch file1 file2 ~/work/gitkBug % git add file1 ~/work/gitkBug % git commit "--author=MrFoo " file1 -m "add file1" ~/work/gitkBug % git add file2 ~/work/gitkBug % git commit "--author=MrBar " file2 -m "add file2" # TEST: git log --author - OK ~/work/gitkBug % git log --author=MrBar # OK, as expected commit 8aa4a4f651162bcb2275a1e9ee23fc1bb7226097 Author: MrBar Date: Tue Apr 26 14:22:58 2016 +0200 add file2 # TEST: gitk --author - OPS ~/work/gitkBug % gitk --author=MrBar # Ops, gitk shows also the parent commit ``` ## Mike Rappazzo, 2016-04-26 14:06 Subject: Re: "gitk --author=foo" shows also parent Message-ID: URL: https://gitlist.dev/e/CANoM8SXn0CgUqQU3vmH-kwuxiDfC1%3D4FCh1SUsYuOOv4fQtWpw%40mail.gmail.com In-Reply-To: <571F6852.1070405@qt.io> ``` On Tue, Apr 26, 2016 at 9:08 AM, Nikolai Kosjar wrote: > Hi! > > $ gitk --author=foo > > ...seems to show also the parent of each author-matched commit, whereas > > $ git log --author=foo > > does not. Is this intended or a bug? I've stumbled over this while > configuring a gitk view with the author field. I believe that this is intentional. Notice that the parent commit's circle is just outlined compared to the selected authored commits are filled. I consider this the context of the commits you are looking at. > > Nikolai > > > > > > # Setup > ~/work/gitkBug % git init . > ~/work/gitkBug % touch file1 file2 > ~/work/gitkBug % git add file1 > ~/work/gitkBug % git commit "--author=MrFoo " file1 -m "add > file1" > ~/work/gitkBug % git add file2 > ~/work/gitkBug % git commit "--author=MrBar " file2 -m "add > file2" > > # TEST: git log --author - OK > ~/work/gitkBug % git log --author=MrBar # OK, as expected > commit 8aa4a4f651162bcb2275a1e9ee23fc1bb7226097 > Author: MrBar > Date: Tue Apr 26 14:22:58 2016 +0200 > > add file2 > > # TEST: gitk --author - OPS > ~/work/gitkBug % gitk --author=MrBar # Ops, gitk shows also the parent > commit > > > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ``` ## Nikolai Kosjar, 2016-04-26 16:12 Subject: Re: "gitk --author=foo" shows also parent Message-ID: <571F9380.4070006@qt.io> URL: https://gitlist.dev/e/571F9380.4070006%40qt.io In-Reply-To: ``` On 04/26/2016 04:06 PM, Mike Rappazzo wrote: > On Tue, Apr 26, 2016 at 9:08 AM, Nikolai Kosjar wrote: >> Hi! >> >> $ gitk --author=foo >> >> ...seems to show also the parent of each author-matched commit, whereas >> >> $ git log --author=foo >> >> does not. Is this intended or a bug? I've stumbled over this while >> configuring a gitk view with the author field. > > I believe that this is intentional. Notice that the parent commit's > circle is just outlined > compared to the selected authored commits are filled. I consider this > the context > of the commits you are looking at. Hmm, then I'm not interested in the context since it's too noisy. Is there any way to suppress this? Nikolai ``` ## Jeff King, 2016-04-26 17:52 Subject: Re: "gitk --author=foo" shows also parent Message-ID: <20160426175243.GA18260@sigill.intra.peff.net> URL: https://gitlist.dev/e/20160426175243.GA18260%40sigill.intra.peff.net In-Reply-To: <571F9380.4070006@qt.io> ``` On Tue, Apr 26, 2016 at 06:12:48PM +0200, Nikolai Kosjar wrote: > >I believe that this is intentional. Notice that the parent commit's > >circle is just outlined > >compared to the selected authored commits are filled. I consider this > >the context > >of the commits you are looking at. > > Hmm, then I'm not interested in the context since it's too noisy. Is there > any way to suppress this? I am not a gitk user, but AFAIK, no. Gitk uses "--boundary" to ask git for the bottom boundary of each string of commits. There is unfortunately no "--no-boundary" option to override this (and I just tried adding one, and it doesn't seem to work; gitk is perhaps too aggressive in the way it passes along --boundary). So I think it would require a patch to gitk. -Peff ```