From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Long Yang <gimmely@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: RE: v2.5.2 installation on Windows 10
Date: Sat, 12 Sep 2015 13:56:29 +0200 [thread overview]
Message-ID: <9fdf16cff4e2468a3a013ac2f13ac060@dscho.org> (raw)
In-Reply-To: <01a501d0ed50$48b19ab0$da14d010$@gmail.com>
Hi Long,
On 2015-09-12 13:43, Long Yang wrote:
> Thanks for the email to confirm the bug.
Of course! Thank you for taking the time to report it.
> To answer your question first, I found only the Community page at
> http://www.git-scm.com/, as I was looking for a forum-kind of page to
> see if someone had reported the same problem I had. Then I tried to
> send a couple of emails to the mailing list, git@vger.kernel.org, as
> instructed on the Community page. But none of my emails was
> delivered. At the end, I post my case via gmane.
Thank you, I think I will open a Pull Request to that Community page to suggest going the GitHub issues route in case of Windows-specific bugs.
> In short, I still don't know how to successfully report a bug for Git.
> Should I/users use GitHub?
If the bug in question is a Windows-specific bug, or if you do not know whether it is a Windows-specific bug, then yes, please submit it to our GitHub issue tracker, as described in the "Contribute" section of our home page: http://git-for-windows.github.io/#contribute
If you already know that the bug in question affects more than just Windows users, please report it to the Git mailing list, as you have done. (You will need to send plain-text messages, as the Git mailing list rejects HTML mails.)
Ciao,
Johannes
next prev parent reply other threads:[~2015-09-12 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 16:13 v2.5.2 installation on Windows 10 Long
2015-09-12 9:34 ` Diaoul
2015-09-12 10:05 ` Johannes Schindelin
2015-09-12 9:57 ` Johannes Schindelin
[not found] ` <01a501d0ed50$48b19ab0$da14d010$@gmail.com>
2015-09-12 11:56 ` Johannes Schindelin [this message]
2015-09-12 14:35 ` Long
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=9fdf16cff4e2468a3a013ac2f13ac060@dscho.org \
--to=johannes.schindelin@gmx.de \
--cc=gimmely@gmail.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).