# Is GGG mislabeling topics? 3 messages from 2023-01-19 to 2023-02-02. Participants: Junio C Hamano, Johannes Schindelin. Thread: https://gitlist.dev/t/59120 ## Junio C Hamano, 2023-01-19 17:32 Subject: Is GGG mislabeling topics? Message-ID: URL: https://gitlist.dev/e/xmqqpmba1ld4.fsf%40gitster.g ``` These comments from GGG bot https://github.com/git/git/pull/1435#issuecomment-1386301994 https://github.com/git/git/pull/1435#issuecomment-1386302018 add 'next' and 'seen' labels, citing merges e3ead5f and c52b021 respectively, but these merges are of a topic that has little to do with this pull request (#1435). Is this expected? ``` ## Johannes Schindelin, 2023-02-02 14:20 Subject: Re: Is GGG mislabeling topics? Message-ID: <52c9ed08-43c3-80c6-32f6-42209b799af6@gmx.de> URL: https://gitlist.dev/e/52c9ed08-43c3-80c6-32f6-42209b799af6%40gmx.de In-Reply-To: ``` Hi Junio, On Thu, 19 Jan 2023, Junio C Hamano wrote: > These comments from GGG bot > > https://github.com/git/git/pull/1435#issuecomment-1386301994 > https://github.com/git/git/pull/1435#issuecomment-1386302018 > > add 'next' and 'seen' labels, citing merges e3ead5f and c52b021 > respectively, but these merges are of a topic that has little to do > with this pull request (#1435). Is this expected? Since I could not make `amlog` work reliably for GitGitGadget (and you will recall that it was not for lack of trying, not by _any_ stretch of imagination, I really, really put in a few weeks and it just turned out that there was no way to come up with a 100% correct record of mappings between patches on the Git mailing list and the commits in git/git), the best I could do was to use `range-diff` to identify which patches made it upstream, and what the upstream OIDs are. What you see in action is that this is imperfect. Because in the absence of actual git/git commits that correspond to the GitGitGadget Pull Requests' commits, `range-diff` will even identify replacements or alternative patches as the git/git commits corresponding to the PR. I don't see how this could be made robust without forcing you to adopt different processes than you are using right now. Ciao, Johannes ``` ## Junio C Hamano, 2023-02-02 17:06 Subject: Re: Is GGG mislabeling topics? Message-ID: URL: https://gitlist.dev/e/xmqqk010uhdr.fsf%40gitster.g In-Reply-To: <52c9ed08-43c3-80c6-32f6-42209b799af6@gmx.de> ``` Johannes Schindelin writes: > On Thu, 19 Jan 2023, Junio C Hamano wrote: > >> These comments from GGG bot >> >> https://github.com/git/git/pull/1435#issuecomment-1386301994 >> https://github.com/git/git/pull/1435#issuecomment-1386302018 >> >> add 'next' and 'seen' labels, citing merges e3ead5f and c52b021 >> respectively, but these merges are of a topic that has little to do >> with this pull request (#1435). Is this expected? > > Since I could not make `amlog` work reliably for GitGitGadget ... "git rev-list e3ead5f^..e3ead5f" (as the comment claims that GGG saw e3ead5f merged this topic) should be able to identify the individual commits merged, in this case three topmost commits from Peff leading to 6c065f72 (http: support CURLOPT_PROTOCOLS_STR, 2023-01-16). > What you see in action is that this is imperfect. Because in the absence > of actual git/git commits that correspond to the GitGitGadget Pull > Requests' commits, `range-diff` will even identify replacements or > alternative patches as the git/git commits corresponding to the PR. Hmph, so the three topmost commits were mistaken to match the patch(es) on this branch. That's sort-of understandable but not very satisfactory. And amlog seems to know the message ID that resulted in that topmost commit that was merged to 'next'. $ git notes --ref notes/amlog show e3ead5f^2 Message-Id: Perhaps GGG can be told to recognise that it is not one of the messages it sent out before, or something? ```