{"thread":{"id":"63273","subject":"Possible git-gui bug","startedAt":"2025-04-09T11:10:37Z","lastAt":"2025-06-18T21:36:41Z","messageCount":7,"participants":["Lauri Reilson","Eric Sunshine"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"515907","messageId":"AS8P191MB2174CB58B1A29D1492EE7842FAB42@AS8P191MB2174.EURP191.PROD.OUTLOOK.COM","threadId":"63273","inReplyTo":null,"subject":"Possible git-gui bug","fromName":"Lauri Reilson","fromEmail":"lauri.reilson@proekspert.ee","sentAt":"2025-04-09T11:10:33Z","receivedAt":"2025-04-09T11:10:37Z","isPatch":false,"sender":{"key":"lauri.reilson@proekspert.ee","avatar":null},"body":"Hello to all!\n\nI have a small issue with git-gui. I added the git-bugreport to the attachement.\n\nWarm regards,\n\nLauri Reilson * Software Engineer\nlauri.reilson@proekspert.ee\nPROEKSPERT * Sõpruse pst 157, 13417 Tallinn, Estonia, EU\n\n\n\nThank you for filling out a Git bug report!\nPlease answer the following questions to help us understand your issue.\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\nAdded files for commiting using git-gui. Provided one line commit message\n\nWhatd did you expect to happen? (Expected behavior)\nExpected to commit using git-gui. Commit message was in the format <#task-id message>. I use \";\" instead of comment symbol as \"#\" is used as a means\nto track task id.\n\nWhat happened instead? (Actual behavior)\nGit-gui gave error message, that I need to provide commit message. Tried one line, folled the error message (first line, blank line, remaining lines).\nAlso, when ammending, git-gui messed up the message. Message was in the form of:\n\n#123456 message\n\n- Some small description\n\nAnd git-gui turned this into:\n- Some small description\n\n\nWhat's different between what you expected and what actually happened?\nCommit message not being what I wrote and not being able to commit.\n\n\nAnything else you want to add:\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n\n[System Info]\ngit version:\ngit version 2.49.0.windows.1\ncpu: x86_64\nsizeof-long: 4\nsizeof-size_t: 8\nshell-path: D:/git-sdk-64-build-installers/usr/bin/sh\nfeature: fsmonitor--daemon\nlibcurl: 8.12.1\nOpenSSL: OpenSSL 3.2.4 11 Feb 2025\nzlib: 1.3.1\nuname: Windows 10.0 26100 \ncompiler info: gnuc: 14.2, msvc\nlibc info: no libc information available\n$SHELL (typically, interactive shell): C:\\Program Files\\Git\\usr\\bin\\bash.exe\n\n\n[Enabled Hooks]\n"},{"id":"515935","messageId":"CAPig+cTK+jz_kF7zd85nVRCn-6sqbH0o7N_ZDtDZDVjYbYgQtQ@mail.gmail.com","threadId":"63273","inReplyTo":"AS8P191MB2174CB58B1A29D1492EE7842FAB42@AS8P191MB2174.EURP191.PROD.OUTLOOK.COM","subject":"Re: Possible git-gui bug","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2025-04-09T19:30:54Z","receivedAt":"2025-04-09T19:31:06Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Wed, Apr 9, 2025 at 7:11 AM Lauri Reilson\n wrote:\n> I have a small issue with git-gui. I added the git-bugreport to the attachement.\n>\n> > Whatd did you expect to happen? (Expected behavior)\n> Expected to commit using git-gui. Commit message was in the format <#task-id message>. I use \";\" instead of comment symbol as \"#\" is used as a means to track task id.\n>\n> > What happened instead? (Actual behavior)\n> Git-gui gave error message, that I need to provide commit message. Tried one line, folled the error message (first line, blank line, remaining lines).\n\nThis sounds like the problem addressed by [1].\n\n[1]: https://lore.kernel.org/git/20250315140913.577422-1-oswald.buddenhagen@gmx.de/\n"},{"id":"517962","messageId":"AS8P191MB2174A636B81F92212F4B0C03FA96A@AS8P191MB2174.EURP191.PROD.OUTLOOK.COM","threadId":"63273","inReplyTo":"CAPig+cTK+jz_kF7zd85nVRCn-6sqbH0o7N_ZDtDZDVjYbYgQtQ@mail.gmail.com","subject":"RE: Possible git-gui bug","fromName":"Lauri Reilson","fromEmail":"lauri.reilson@proekspert.ee","sentAt":"2025-05-13T18:09:11Z","receivedAt":"2025-05-13T18:09:16Z","isPatch":false,"sender":{"key":"lauri.reilson@proekspert.ee","avatar":null},"body":"Hi, Eric!\n\nSorry for this long response. Thank you for the information. Unfortunately, I don't follow quite well. Is this thing going to be fixed or not?\nIt has become quite annoying that I cannot make commits with git-gui and there hasn't been any updates.\n\nBest regards,\n\nLauri Reilson • Software Engineer\nlauri.reilson@proekspert.ee\nPROEKSPERT • Sõpruse pst 157, 13417 Tallinn, Estonia, EU\n\n-----Original Message-----\nFrom: Eric Sunshine \nSent: Wednesday, April 9, 2025 10:31 PM\nTo: Lauri Reilson \nCc: git@vger.kernel.org\nSubject: Re: Possible git-gui bug\n\nOn Wed, Apr 9, 2025 at 7:11 AM Lauri Reilson wrote:\n> I have a small issue with git-gui. I added the git-bugreport to the attachement.\n>\n> > Whatd did you expect to happen? (Expected behavior)\n> Expected to commit using git-gui. Commit message was in the format <#task-id message>. I use \";\" instead of comment symbol as \"#\" is used as a means to track task id.\n>\n> > What happened instead? (Actual behavior)\n> Git-gui gave error message, that I need to provide commit message. Tried one line, folled the error message (first line, blank line, remaining lines).\n\nThis sounds like the problem addressed by [1].\n\n[1]: https://lore.kernel.org/git/20250315140913.577422-1-oswald.buddenhagen@gmx.de/\n"},{"id":"517964","messageId":"CAPig+cR4Jb0w=McwobCrtySD1nH8sF6rv7MGduQ-yVsRUHHSBg@mail.gmail.com","threadId":"63273","inReplyTo":"AS8P191MB2174A636B81F92212F4B0C03FA96A@AS8P191MB2174.EURP191.PROD.OUTLOOK.COM","subject":"Re: Possible git-gui bug","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2025-05-13T18:32:06Z","receivedAt":"2025-05-13T18:32:20Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Tue, May 13, 2025 at 2:09 PM Lauri Reilson\n wrote:\n> > From: Eric Sunshine \n> > On Wed, Apr 9, 2025 at 7:11 AM Lauri Reilson wrote:\n> > > I have a small issue with git-gui. I added the git-bugreport to the attachement.\n> > > Expected to commit using git-gui. Commit message was in the format <#task-id message>. I use \";\" instead of comment symbol as \"#\" is used as a means to track task id.\n> > >\n> > > > What happened instead? (Actual behavior)\n> > > Git-gui gave error message, that I need to provide commit message. Tried one line, folled the error message (first line, blank line, remaining lines).\n> >\n> > This sounds like the problem addressed by [1].\n> >\n> > [1]: https://lore.kernel.org/git/20250315140913.577422-1-oswald.buddenhagen@gmx.de/\n>\n> Sorry for this long response. Thank you for the information.\n> Unfortunately, I don't follow quite well. Is this thing going to be\n> fixed or not?\n\nIt appears that the maintainer of git-gui, Johannes Sixt, applied the\npatch mentioned above to his git-gui tree[*] and that Junio already\npulled the fix from Johannes's tree into the Git tree. Although the\nfix hasn't yet made it into a Git release, Junio has already promoted\nthe fix to his \"main\" branch which means it will likely be part of the\nnext Git release.\n\n> It has become quite annoying that I cannot make commits with git-gui\n> and there hasn't been any updates.\n\nIt would be helpful if you could try applying the patch mentioned\nabove to your local git-gui installation and report back here whether\nit indeed fixes the problem you are experiencing. If it does not fix\nthe problem, then my supposition was wrong about the mentioned patch\nbeing related to the problem you reported. If you're not in a position\nto try the patch locally before the next Git release, then perhaps the\nbest you can do is wait for the next Git release and report back\nwhether it fixes the problem you're experiencing.\n\n[*] https://github.com/j6t/git-gui/commit/6b43a57dfce1e5acd85f7a8365c080b6fc4f8645\n"},{"id":"517966","messageId":"AS8P191MB2174D9A6C109202A5195CAA2FA96A@AS8P191MB2174.EURP191.PROD.OUTLOOK.COM","threadId":"63273","inReplyTo":"CAPig+cR4Jb0w=McwobCrtySD1nH8sF6rv7MGduQ-yVsRUHHSBg@mail.gmail.com","subject":"RE: Possible git-gui bug","fromName":"Lauri Reilson","fromEmail":"lauri.reilson@proekspert.ee","sentAt":"2025-05-13T18:35:00Z","receivedAt":"2025-05-13T18:35:03Z","isPatch":false,"sender":{"key":"lauri.reilson@proekspert.ee","avatar":null},"body":"Thank you, Eric!\n\nI'll try it and get back to you. It will take some time. Possibly next week.\n\nWarm regards,\n\nLauri Reilson • Software Engineer\nlauri.reilson@proekspert.ee\nPROEKSPERT • Sõpruse pst 157, 13417 Tallinn, Estonia, EU\n\n-----Original Message-----\nFrom: Eric Sunshine \nSent: Tuesday, May 13, 2025 9:32 PM\nTo: Lauri Reilson \nCc: git@vger.kernel.org\nSubject: Re: Possible git-gui bug\n\nOn Tue, May 13, 2025 at 2:09 PM Lauri Reilson wrote:\n> > From: Eric Sunshine On Wed, Apr 9, 2025 at \n> > 7:11 AM Lauri Reilson wrote:\n> > > I have a small issue with git-gui. I added the git-bugreport to the attachement.\n> > > Expected to commit using git-gui. Commit message was in the format <#task-id message>. I use \";\" instead of comment symbol as \"#\" is used as a means to track task id.\n> > >\n> > > > What happened instead? (Actual behavior)\n> > > Git-gui gave error message, that I need to provide commit message. Tried one line, folled the error message (first line, blank line, remaining lines).\n> >\n> > This sounds like the problem addressed by [1].\n> >\n> > [1]: \n> > https://lore.kernel.org/git/20250315140913.577422-1-oswald.buddenhag\n> > en@gmx.de/\n>\n> Sorry for this long response. Thank you for the information.\n> Unfortunately, I don't follow quite well. Is this thing going to be \n> fixed or not?\n\nIt appears that the maintainer of git-gui, Johannes Sixt, applied the patch mentioned above to his git-gui tree[*] and that Junio already pulled the fix from Johannes's tree into the Git tree. Although the fix hasn't yet made it into a Git release, Junio has already promoted the fix to his \"main\" branch which means it will likely be part of the next Git release.\n\n> It has become quite annoying that I cannot make commits with git-gui \n> and there hasn't been any updates.\n\nIt would be helpful if you could try applying the patch mentioned above to your local git-gui installation and report back here whether it indeed fixes the problem you are experiencing. If it does not fix the problem, then my supposition was wrong about the mentioned patch being related to the problem you reported. If you're not in a position to try the patch locally before the next Git release, then perhaps the best you can do is wait for the next Git release and report back whether it fixes the problem you're experiencing.\n\n[*] https://github.com/j6t/git-gui/commit/6b43a57dfce1e5acd85f7a8365c080b6fc4f8645\n"},{"id":"520372","messageId":"AS8P191MB2174894CB42C62AC32F63DD5FA72A@AS8P191MB2174.EURP191.PROD.OUTLOOK.COM","threadId":"63273","inReplyTo":"AS8P191MB2174D9A6C109202A5195CAA2FA96A@AS8P191MB2174.EURP191.PROD.OUTLOOK.COM","subject":"RE: Possible git-gui bug","fromName":"Lauri Reilson","fromEmail":"lauri.reilson@proekspert.ee","sentAt":"2025-06-18T21:29:44Z","receivedAt":"2025-06-18T21:29:49Z","isPatch":false,"sender":{"key":"lauri.reilson@proekspert.ee","avatar":null},"body":"Hi, Eric!\n\nI know I promised to check that patch out and get back to you. The first pard I had no time to do. However, I have installed the latest Git version (2.50.0) and my problem is fixed. Thank you for that.\n\nHave an awesome summer!\n\nLauri Reilson • Software Engineer\nlauri.reilson@proekspert.ee\nPROEKSPERT • Sõpruse pst 157, 13417 Tallinn, Estonia, EU\n\n-----Original Message-----\nFrom: Lauri Reilson \nSent: Tuesday, May 13, 2025 9:35 PM\nTo: Eric Sunshine \nCc: git@vger.kernel.org\nSubject: RE: Possible git-gui bug\n\nThank you, Eric!\n\nI'll try it and get back to you. It will take some time. Possibly next week.\n\nWarm regards,\n\nLauri Reilson • Software Engineer\nlauri.reilson@proekspert.ee\nPROEKSPERT • Sõpruse pst 157, 13417 Tallinn, Estonia, EU\n\n-----Original Message-----\nFrom: Eric Sunshine \nSent: Tuesday, May 13, 2025 9:32 PM\nTo: Lauri Reilson \nCc: git@vger.kernel.org\nSubject: Re: Possible git-gui bug\n\nOn Tue, May 13, 2025 at 2:09 PM Lauri Reilson wrote:\n> > From: Eric Sunshine On Wed, Apr 9, 2025 at\n> > 7:11 AM Lauri Reilson wrote:\n> > > I have a small issue with git-gui. I added the git-bugreport to the attachement.\n> > > Expected to commit using git-gui. Commit message was in the format <#task-id message>. I use \";\" instead of comment symbol as \"#\" is used as a means to track task id.\n> > >\n> > > > What happened instead? (Actual behavior)\n> > > Git-gui gave error message, that I need to provide commit message. Tried one line, folled the error message (first line, blank line, remaining lines).\n> >\n> > This sounds like the problem addressed by [1].\n> >\n> > [1]: \n> > https://lore.kernel.org/git/20250315140913.577422-1-oswald.buddenhag\n> > en@gmx.de/\n>\n> Sorry for this long response. Thank you for the information.\n> Unfortunately, I don't follow quite well. Is this thing going to be \n> fixed or not?\n\nIt appears that the maintainer of git-gui, Johannes Sixt, applied the patch mentioned above to his git-gui tree[*] and that Junio already pulled the fix from Johannes's tree into the Git tree. Although the fix hasn't yet made it into a Git release, Junio has already promoted the fix to his \"main\" branch which means it will likely be part of the next Git release.\n\n> It has become quite annoying that I cannot make commits with git-gui \n> and there hasn't been any updates.\n\nIt would be helpful if you could try applying the patch mentioned above to your local git-gui installation and report back here whether it indeed fixes the problem you are experiencing. If it does not fix the problem, then my supposition was wrong about the mentioned patch being related to the problem you reported. If you're not in a position to try the patch locally before the next Git release, then perhaps the best you can do is wait for the next Git release and report back whether it fixes the problem you're experiencing.\n\n[*] https://github.com/j6t/git-gui/commit/6b43a57dfce1e5acd85f7a8365c080b6fc4f8645\n"},{"id":"520374","messageId":"CAPig+cRW+dmj3j23oSRc=nBnwFM6zTJ=WR=1vZScnxycFS3tqA@mail.gmail.com","threadId":"63273","inReplyTo":"AS8P191MB2174894CB42C62AC32F63DD5FA72A@AS8P191MB2174.EURP191.PROD.OUTLOOK.COM","subject":"Re: Possible git-gui bug","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2025-06-18T21:36:29Z","receivedAt":"2025-06-18T21:36:41Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Wed, Jun 18, 2025 at 5:29 PM Lauri Reilson\n wrote:\n> Hi, Eric!\n>\n> I know I promised to check that patch out and get back to you. The first pard I had no time to do. However, I have installed the latest Git version (2.50.0) and my problem is fixed. Thank you for that.\n\nThanks for reporting back that Oswald's patch[*] did indeed fix the\nproblem you reported.\n\n[*]: https://lore.kernel.org/git/20250315140913.577422-1-oswald.buddenhagen@gmx.de/\n"}]}