From: Bryan Jacobs <bjacobs@woti.com>
To: Jeff King <peff@peff.net>
Cc: Scott Chacon <schacon@gmail.com>, git@vger.kernel.org
Subject: Re: git bug reporting
Date: Mon, 29 Aug 2011 15:34:48 -0400 [thread overview]
Message-ID: <20110829153448.190baaa1@robyn.woti.com> (raw)
In-Reply-To: <20110829192618.GF756@sigill.intra.peff.net>
On Mon, 29 Aug 2011 15:26:18 -0400
Jeff King <peff@peff.net> wrote:
> On Mon, Aug 29, 2011 at 01:20:52PM -0400, Bryan Jacobs wrote:
>
> > Dear git Developers,
> >
> > Apologies if this is not the right forum for bug reports. I was
> > unable to find a Bugzilla/Redmine/Flyspray instance for issue
> > maintenance, nor some "proper procedure" on the git web page.
>
> Yes, this is the right place. This question seems to be coming up a
> lot lately. And indeed, looking at the webpage and the wiki, we are
> not very clear that the mailing list is the place for such things.
>
> Do you mind telling us where you looked? That will give us at least
> one spot that we know should be more clear. :)
I looked at the git-scm.com main page, the "documentation" sub-page,
the wiki front page, and googled the site for terms like "issue tracker"
and "bug reports", then read the FAQ.
> In the meantime, I've updated:
>
> 1. The GitCommunity wiki page to mention that bug reports should go
> to the list.
>
> 2. Added an entry "How do I report a bug in git?" to the FAQ on the
> wiki.
>
> 3. Sent Scott a patch for git-scm.org to mention bug reporting under
> the big "Got questions" banner on the front page that points
> people to the mailing list. Pull request is here:
>
> https://github.com/schacon/gitscm/pull/11
>
> It may make sense to have a specific page on reporting bugs, and
> link to it via a bigger "how to report bugs" somewhere on the
> front page of git-scm.org.
Thank you very much for your efforts. It looks like you hit all but one
of the places I looked. I agree that having a link from some part of the
git-scm landing page would make sense, that's common practice for
software projects and seems to me a logical place for it. I (obviously)
read the text under the "got questions" bit; it was what sent me to
this list. If it had said "report a bug here" I would have felt more
confident about sending this message.
Bryan Jacobs
next prev parent reply other threads:[~2011-08-29 19:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 17:20 git-svn and mergeinfo Bryan Jacobs
2011-08-29 19:26 ` git bug reporting Jeff King
2011-08-29 19:34 ` Bryan Jacobs [this message]
2011-08-29 20:44 ` Junio C Hamano
2011-08-31 14:03 ` Sverre Rabbelier
2011-08-31 13:59 ` git-svn and mergeinfo Sverre Rabbelier
2011-08-31 16:55 ` Bryan Jacobs
2011-08-31 17:01 ` Sverre Rabbelier
2011-09-01 8:59 ` Michael Haggerty
2011-09-01 14:43 ` Bryan Jacobs
2011-09-01 16:00 ` Junio C Hamano
2011-09-06 12:56 ` Carlos Martín Nieto
2011-09-06 13:52 ` Bryan Jacobs
2011-09-06 14:28 ` Carlos Martín Nieto
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=20110829153448.190baaa1@robyn.woti.com \
--to=bjacobs@woti.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=schacon@gmail.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;
as well as URLs for NNTP newsgroup(s).