This issue tracker is for project ideas, *not for bug reports*

[dscho]

This is not the place the Git projects expects bug reports: please send them to the Git mailing list. See https://git-scm.com/community for more details.

[DenizThatMenace]

Is there a trick for how to get the attention of any Git developer for a bug report on the Git mailing list?

I added my bug report in this issue tracker in the hope it might automatically get forwarded to the Git mailing list (similar to the PRs) and therefore might get some attention by the right Git developer.

Especially, because I already tried differently: Almost a year ago, I already posted that bug report on the Git mailing list, however, it did not get any attention. (It probably got lost between all the automated emails with patches for new features.)

I would really much appreciate if that bug report could get to the attention of some Git developer. 🥺

[phil-blain]

Is there a trick for how to get the attention of any Git developer for a bug report on the Git mailing list?

There is no universal trick. But here are some guidelines.

1. If your bug is a regression, and you can bisect to find out which commit introduced the regression, then CC-ing the author of that commit is a good idea. Usually developers are willing to fix something they broke.
2. Try to make your bug report as concise as possible, and include a complete reproducer (i.e. a sequence of commands starting with git init or git clone).
3. If you know that some developer has an interest in the area/command that your bug report relates to, it's also a good idea to CC them (of course, you must follow the list a bit to know who works on / is interested in what).
4. If you can, try to debug the problem yourself, and write up your findings in your email.

(It probably got lost between all the automated emails with patches for new features.)

Most patch emails on the Git mailing list are not automated, they are sent using git format-patch and git send-email by developers themselves. Some developer do use Gitgitgadget to send GitHub PRs as patch series to the list, but it's not the majority.

Note also that if you send your bug report close to a release date, people might be busy finalizing the release and might pay less attentions to bug reports.

Hope that helps! :)

EDIT I fixed the link to the Git calendar

[dscho]

I already posted that bug report on the Git mailing list, however, it did not get any attention. (It probably got lost between all the automated emails with patches for new features.)

@Bagira80 I hear your frustration. For what it's worth, I understand your frustration and also wish that things like that wouldn't happen.

[TaoK]

Insofar as issues (Ideas) here might be orphaned by their original authors, who is/are the maintainers to contact if/when they should be closed? Is this yet another thing you do, @dscho?

[dscho]

Is this yet another thing you do, @dscho?

I suppose it is 😆