{"thread":{"id":"58198","subject":"What is the URL of git's bug tracker?","startedAt":"2022-07-21T03:07:42Z","lastAt":"2022-07-21T18:01:22Z","messageCount":5,"participants":["Yuri","Konstantin Khomoutov","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"459563","messageId":"a5f48218-94ad-195e-97bc-b29c4a588903@tsoft.com","threadId":"58198","inReplyTo":null,"subject":"What is the URL of git's bug tracker?","fromName":"Yuri","fromEmail":"yuri@rawbw.com","sentAt":"2022-07-21T03:07:37Z","receivedAt":"2022-07-21T03:07:42Z","isPatch":false,"sender":{"key":"yuri@rawbw.com","avatar":null},"body":"\nThanks,\n\nYuri\n\n\n"},{"id":"459606","messageId":"20220721101948.2i3nyroxrexg4voi@carbon","threadId":"58198","inReplyTo":"a5f48218-94ad-195e-97bc-b29c4a588903@tsoft.com","subject":"Re: What is the URL of git's bug tracker?","fromName":"Konstantin Khomoutov","fromEmail":"kostix@bswap.ru","sentAt":"2022-07-21T10:19:48Z","receivedAt":"2022-07-21T10:20:07Z","isPatch":false,"sender":{"key":"kostix@bswap.ru","avatar":null},"body":"There is none - please read https://git-scm.com/community\n\nJFTR note that the Windows port of Git does have a bug tracker hosted\non Github: https://github.com/git-for-windows/git/issues\n\n"},{"id":"459660","messageId":"98dc2e8e-58b6-80ad-65da-2bd1cc5dffc2@tsoft.com","threadId":"58198","inReplyTo":"20220721101948.2i3nyroxrexg4voi@carbon","subject":"Re: What is the URL of git's bug tracker?","fromName":"Yuri","fromEmail":"yuri@rawbw.com","sentAt":"2022-07-21T16:49:22Z","receivedAt":"2022-07-21T16:49:31Z","isPatch":false,"sender":{"key":"yuri@rawbw.com","avatar":null},"body":"On 7/21/22 03:19, Konstantin Khomoutov wrote:\n> There is none - please read https://git-scm.com/community\n\n\nOn 04-09-2021 I reported to this ML the bug that git-2.31.0 printed \nstray messages during 'git stash push' command.\n\n\ngit stash push -- x11-toolkits/fltk\nSaved working directory and index state WIP on main: 4c2cc95952a6 \ngraphics/mesa-devel: update to 21.0.b.4390\n<stdin>:83: space before tab in indent.\n      LIBS=\"$LIBS -lX11 $X_EXTRA_LIBS\"\n<stdin>:84: space before tab in indent.\n      CFLAGS=\"$CFLAGS $X_CFLAGS\"\n<stdin>:85: space before tab in indent.\n      CXXFLAGS=\"$CXXFLAGS $X_CFLAGS\"\n<stdin>:88: space before tab in indent.\n      DSOFLAGS=\"$X_LIBS $DSOFLAGS\"\n<stdin>:89: space before tab in indent.\n      $as_echo \"#define USE_X11 1\" >>confdefs.h\nwarning: squelched 40 whitespace errors\nwarning: 45 lines add whitespace errors.\n\n\nNow in git-2.37.1 this bug is still there,\n\n\nIs it forgotten about? Is the fix planned? Is it fixed but not yet released?\n\nIt's impossible to say without a bug tracker.\n\n\n\nYuri\n\n\n"},{"id":"459669","messageId":"xmqqfsiuicv5.fsf@gitster.g","threadId":"58198","inReplyTo":"98dc2e8e-58b6-80ad-65da-2bd1cc5dffc2@tsoft.com","subject":"Re: What is the URL of git's bug tracker?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-07-21T17:39:42Z","receivedAt":"2022-07-21T17:39:47Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Yuri <yuri@rawbw.com> writes:\n\n> On 7/21/22 03:19, Konstantin Khomoutov wrote:\n>> There is none - please read https://git-scm.com/community\n>\n>\n> On 04-09-2021 I reported to this ML the bug that git-2.31.0 printed\n> stray messages during 'git stash push' command.\n>\n>\n> git stash push -- x11-toolkits/fltk\n> Saved working directory and index state WIP on main: 4c2cc95952a6\n> graphics/mesa-devel: update to 21.0.b.4390\n> <stdin>:83: space before tab in indent.\n>      LIBS=\"$LIBS -lX11 $X_EXTRA_LIBS\"\n> <stdin>:84: space before tab in indent.\n>      CFLAGS=\"$CFLAGS $X_CFLAGS\"\n> <stdin>:85: space before tab in indent.\n>      CXXFLAGS=\"$CXXFLAGS $X_CFLAGS\"\n> <stdin>:88: space before tab in indent.\n>      DSOFLAGS=\"$X_LIBS $DSOFLAGS\"\n> <stdin>:89: space before tab in indent.\n>      $as_echo \"#define USE_X11 1\" >>confdefs.h\n> warning: squelched 40 whitespace errors\n> warning: 45 lines add whitespace errors.\n>\n>\n> Now in git-2.37.1 this bug is still there,\n>\n>\n> Is it forgotten about? Is the fix planned? Is it fixed but not yet released?\n>\n> It's impossible to say without a bug tracker.\n>\n>\n>\n> Yuri\n\nIs there aything to be \"fixed\" in the first place?  What the\ntranscript shows is that the user tried to run \"git stash push\" and\nin the process of creating the stash, it noticed whitespace errors\nin the files that are being modified and reported, which is not\nsomething that is unexpected.  It does not look like a bug.\n\nAt the end, after showing the \"warning: 45 lines...\", perhaps\nsomething else happened that was not described in the report, like\n\"the stash was not created\"?  If so that may be a bug, but it is\nunclear if that is what the complaint is about, so...\n\n\n"},{"id":"459675","messageId":"20220721180114.xruauebr3sbhd5pm@carbon","threadId":"58198","inReplyTo":"98dc2e8e-58b6-80ad-65da-2bd1cc5dffc2@tsoft.com","subject":"Re: What is the URL of git's bug tracker?","fromName":"Konstantin Khomoutov","fromEmail":"kostix@bswap.ru","sentAt":"2022-07-21T18:01:14Z","receivedAt":"2022-07-21T18:01:22Z","isPatch":false,"sender":{"key":"kostix@bswap.ru","avatar":null},"body":"On Thu, Jul 21, 2022 at 09:49:22AM -0700, Yuri wrote:\n\n[...]\n\n> On 04-09-2021 I reported to this ML the bug that git-2.31.0 printed stray\n> messages during 'git stash push' command.\n\nLooks like it's [1].\n\n[...]\n> Now in git-2.37.1 this bug is still there,\n> Is it forgotten about? Is the fix planned? Is it fixed but not yet released?\n> \n> It's impossible to say without a bug tracker.\n\nWell, I'm going to share your pain on this but honestly, from personal\nexperience with F/OSS, I can say that a conventional bug tracker is not going\nto help much in cases like yours: if this problem has been filed as an issue\nthe only things it would gain is some ID attached and a web page available.\nI mean, it would not somehow move it closer to getting fixed - simply due to\nthe apparent lack of interest among those familiar with the code.\nHence at best it would just sit there, and at worst - closed by some bot due\nto lack of activity.\n\nBy the way, if you're interested you could search the ML archives for past\ndiscussions of this topic. For an example, see [2].\n\n\n 1. https://public-inbox.org/git/e493ca9b-c686-68ea-cd8d-c7b13766d65e@rawbw.com/\n 2. https://lore.kernel.org/git/211023.861r4ck8jw.gmgdl@evledraar.gmail.com/\n\n"}]}