What is the URL of git's bug tracker?

Thanks,

Yuri

There is none - please read https://git-scm.com/community

JFTR note that the Windows port of Git does have a bug tracker hosted on Github: https://github.com/git-for-windows/git/issues

On 7/21/22 03:19, Konstantin Khomoutov wrote:

On 04-09-2021 I reported to this ML the bug that git-2.31.0 printed stray messages during 'git stash push' command.

git stash push -- x11-toolkits/fltk
Saved working directory and index state WIP on main: 4c2cc95952a6 
graphics/mesa-devel: update to 21.0.b.4390
<stdin>:83: space before tab in indent.
      LIBS="$LIBS -lX11 $X_EXTRA_LIBS"
<stdin>:84: space before tab in indent.
      CFLAGS="$CFLAGS $X_CFLAGS"
<stdin>:85: space before tab in indent.
      CXXFLAGS="$CXXFLAGS $X_CFLAGS"
<stdin>:88: space before tab in indent.
      DSOFLAGS="$X_LIBS $DSOFLAGS"
<stdin>:89: space before tab in indent.
      $as_echo "#define USE_X11 1" >>confdefs.h
warning: squelched 40 whitespace errors
warning: 45 lines add whitespace errors.

Now in git-2.37.1 this bug is still there,

Is it forgotten about? Is the fix planned? Is it fixed but not yet released?

It's impossible to say without a bug tracker.

Yuri

Yuri <yuri@rawbw.com> writes:

Is there aything to be "fixed" in the first place? What the transcript shows is that the user tried to run "git stash push" and in the process of creating the stash, it noticed whitespace errors in the files that are being modified and reported, which is not something that is unexpected. It does not look like a bug.

At the end, after showing the "warning: 45 lines...", perhaps something else happened that was not described in the report, like "the stash was not created"? If so that may be a bug, but it is unclear if that is what the complaint is about, so...

On Thu, Jul 21, 2022 at 09:49:22AM -0700, Yuri wrote:

[...]

Looks like it's [1].

[...]

Well, I'm going to share your pain on this but honestly, from personal experience with F/OSS, I can say that a conventional bug tracker is not going to help much in cases like yours: if this problem has been filed as an issue the only things it would gain is some ID attached and a web page available. I mean, it would not somehow move it closer to getting fixed - simply due to the apparent lack of interest among those familiar with the code. Hence at best it would just sit there, and at worst - closed by some bot due to lack of activity.

By the way, if you're interested you could search the ML archives for past discussions of this topic. For an example, see [2].

 1. https://public-inbox.org/git/e493ca9b-c686-68ea-cd8d-c7b13766d65e@rawbw.com/
 2. https://lore.kernel.org/git/211023.861r4ck8jw.gmgdl@evledraar.gmail.com/