{"thread":{"id":"42148","subject":"\"gitk --author=foo\" shows also parent","startedAt":"2016-04-26T13:08:34Z","lastAt":"2016-04-26T17:52:44Z","messageCount":4,"participants":["Nikolai Kosjar","Mike Rappazzo","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"284522","messageId":"571F6852.1070405@qt.io","threadId":"42148","inReplyTo":null,"subject":"\"gitk --author=foo\" shows also parent","fromName":"Nikolai Kosjar","fromEmail":"nikolai.kosjar@qt.io","sentAt":"2016-04-26T13:08:34Z","receivedAt":"2016-04-26T13:08:34Z","isPatch":false,"sender":{"key":"nikolai.kosjar@qt.io","avatar":null},"body":"Hi!\n\n\t$ gitk --author=foo\n\n...seems to show also the parent of each author-matched commit, whereas\n\n\t$ git log --author=foo\n\ndoes not. Is this intended or a bug? I've stumbled over this while \nconfiguring a gitk view with the author field.\n\nNikolai\n\n\n\n\n\n# Setup\n~/work/gitkBug % git init .\n~/work/gitkBug % touch file1 file2\n~/work/gitkBug % git add file1\n~/work/gitkBug % git commit \"--author=MrFoo \" file1 -m \"add \nfile1\"\n~/work/gitkBug % git add file2\n~/work/gitkBug % git commit \"--author=MrBar \" file2 -m \"add \nfile2\"\n\n# TEST: git log --author - OK\n~/work/gitkBug % git log --author=MrBar # OK, as expected\ncommit 8aa4a4f651162bcb2275a1e9ee23fc1bb7226097\nAuthor: MrBar \nDate: Tue Apr 26 14:22:58 2016 +0200\n\n add file2\n\n# TEST: gitk --author - OPS\n~/work/gitkBug % gitk --author=MrBar # Ops, gitk shows also the parent \ncommit\n"},{"id":"284524","messageId":"CANoM8SXn0CgUqQU3vmH-kwuxiDfC1=4FCh1SUsYuOOv4fQtWpw@mail.gmail.com","threadId":"42148","inReplyTo":"571F6852.1070405@qt.io","subject":"Re: \"gitk --author=foo\" shows also parent","fromName":"Mike Rappazzo","fromEmail":"rappazzo@gmail.com","sentAt":"2016-04-26T14:06:02Z","receivedAt":"2016-04-26T14:06:02Z","isPatch":false,"sender":{"key":"rappazzo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/525287?v=4"},"body":"On Tue, Apr 26, 2016 at 9:08 AM, Nikolai Kosjar wrote:\n> Hi!\n>\n> $ gitk --author=foo\n>\n> ...seems to show also the parent of each author-matched commit, whereas\n>\n> $ git log --author=foo\n>\n> does not. Is this intended or a bug? I've stumbled over this while\n> configuring a gitk view with the author field.\n\nI believe that this is intentional. Notice that the parent commit's\ncircle is just outlined\ncompared to the selected authored commits are filled. I consider this\nthe context\nof the commits you are looking at.\n\n>\n> Nikolai\n>\n>\n>\n>\n>\n> # Setup\n> ~/work/gitkBug % git init .\n> ~/work/gitkBug % touch file1 file2\n> ~/work/gitkBug % git add file1\n> ~/work/gitkBug % git commit \"--author=MrFoo \" file1 -m \"add\n> file1\"\n> ~/work/gitkBug % git add file2\n> ~/work/gitkBug % git commit \"--author=MrBar \" file2 -m \"add\n> file2\"\n>\n> # TEST: git log --author - OK\n> ~/work/gitkBug % git log --author=MrBar # OK, as expected\n> commit 8aa4a4f651162bcb2275a1e9ee23fc1bb7226097\n> Author: MrBar \n> Date: Tue Apr 26 14:22:58 2016 +0200\n>\n> add file2\n>\n> # TEST: gitk --author - OPS\n> ~/work/gitkBug % gitk --author=MrBar # Ops, gitk shows also the parent\n> commit\n>\n>\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\n"},{"id":"284531","messageId":"571F9380.4070006@qt.io","threadId":"42148","inReplyTo":"CANoM8SXn0CgUqQU3vmH-kwuxiDfC1=4FCh1SUsYuOOv4fQtWpw@mail.gmail.com","subject":"Re: \"gitk --author=foo\" shows also parent","fromName":"Nikolai Kosjar","fromEmail":"nikolai.kosjar@qt.io","sentAt":"2016-04-26T16:12:48Z","receivedAt":"2016-04-26T16:12:48Z","isPatch":false,"sender":{"key":"nikolai.kosjar@qt.io","avatar":null},"body":"On 04/26/2016 04:06 PM, Mike Rappazzo wrote:\n> On Tue, Apr 26, 2016 at 9:08 AM, Nikolai Kosjar wrote:\n>> Hi!\n>>\n>> $ gitk --author=foo\n>>\n>> ...seems to show also the parent of each author-matched commit, whereas\n>>\n>> $ git log --author=foo\n>>\n>> does not. Is this intended or a bug? I've stumbled over this while\n>> configuring a gitk view with the author field.\n>\n> I believe that this is intentional. Notice that the parent commit's\n> circle is just outlined\n> compared to the selected authored commits are filled. I consider this\n> the context\n> of the commits you are looking at.\n\nHmm, then I'm not interested in the context since it's too noisy. Is \nthere any way to suppress this?\n\nNikolai\n"},{"id":"284555","messageId":"20160426175243.GA18260@sigill.intra.peff.net","threadId":"42148","inReplyTo":"571F9380.4070006@qt.io","subject":"Re: \"gitk --author=foo\" shows also parent","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-04-26T17:52:44Z","receivedAt":"2016-04-26T17:52:44Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Apr 26, 2016 at 06:12:48PM +0200, Nikolai Kosjar wrote:\n\n> >I believe that this is intentional. Notice that the parent commit's\n> >circle is just outlined\n> >compared to the selected authored commits are filled. I consider this\n> >the context\n> >of the commits you are looking at.\n> \n> Hmm, then I'm not interested in the context since it's too noisy. Is there\n> any way to suppress this?\n\nI am not a gitk user, but AFAIK, no. Gitk uses \"--boundary\" to ask git\nfor the bottom boundary of each string of commits. There is\nunfortunately no \"--no-boundary\" option to override this (and I just\ntried adding one, and it doesn't seem to work; gitk is perhaps too\naggressive in the way it passes along --boundary).\n\nSo I think it would require a patch to gitk.\n\n-Peff\n"}]}