From: Konstantin Khomoutov <kostix@bswap.ru>
To: Yuri <yuri@rawbw.com>
Cc: Konstantin Khomoutov <kostix@bswap.ru>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: What is the URL of git's bug tracker?
Date: Thu, 21 Jul 2022 21:01:14 +0300 [thread overview]
Message-ID: <20220721180114.xruauebr3sbhd5pm@carbon> (raw)
In-Reply-To: <98dc2e8e-58b6-80ad-65da-2bd1cc5dffc2@tsoft.com>
On Thu, Jul 21, 2022 at 09:49:22AM -0700, Yuri 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.
Looks like it's [1].
[...]
> 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.
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/
prev parent reply other threads:[~2022-07-21 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 3:07 What is the URL of git's bug tracker? Yuri
2022-07-21 10:19 ` Konstantin Khomoutov
2022-07-21 16:49 ` Yuri
2022-07-21 17:39 ` Junio C Hamano
2022-07-21 18:01 ` Konstantin Khomoutov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220721180114.xruauebr3sbhd5pm@carbon \
--to=kostix@bswap.ru \
--cc=git@vger.kernel.org \
--cc=yuri@rawbw.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox