git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git.txt: mention mailing list archive

From
Taylor Blau <me@ttaylorr.com>
Date
Sep 26, 2018, 13:47 UTC
Message-ID
<20180926134717.GC25697@syl>
In-Reply-To
<CAN0heSqA192U-eH8CZJJbKNcimPYxqn6yva6mstsEHnH1-DEGA@mail.gmail.com>
On Wed, Sep 26, 2018 at 10:05:29AM +0200, Martin Ågren wrote:
Show 31 quoted lines
> On Thu, 20 Sep 2018 at 21:07, Junio C Hamano <gitster@pobox.com> wrote:
> >
> > Martin Ågren <martin.agren@gmail.com> writes:
> >
> > > In the "Reporting Bugs" section of git(1), we refer to the mailing list,
> > > but we do not give any hint about where the archives might be found.
> >
> > And why is it a good idea to give that information in Reporting Bugs
> > section?  Are we asking the bug reporters to look for similar issues
> > in the archive before they send their message?  If so, I think that
>
> Your guess is correct, sorry for forcing you to make one.
>
> > we should be explicit about it, too.  Otherwise, the list archive
> > location would look like an irrelevant noise to those who wanted to
> > find the address to report bugs to.
> >
> > For example, we can say something like this:
> >
> > >  Report bugs to the Git mailing list <git@vger.kernel.org> where the
> > >  development and maintenance is primarily done.  You do not have to be
> > >  subscribed to the list to send a message there.
> >   +If you want to check to see if the issue has
> >   +been reported already, the list archive can be found at
> >   +<https://public-inbox.org/git/> and other places.
>
> I think that one reason I avoided spelling out why giving the archive
> location was a good thing to do, was that I didn't want to begin a huge
> list of "please do this and that", scaring away potential bug reporters.
> I think your "If you want to" solves that problem very nicely. I'll wrap
> this up later today.

Yeah. This is a tricky issue in my mind. On the one hand, getting a deluge of duplicate bug reports is a burden for people who actively read and respond to the list. On the other hand, imposing such a burden on bug reporters is a detriment to Git users, who wouldn't benefit from the fixes that would come with good bug reports.

But I think that the above is only a problem if bug reporters are consistently ignoring this advice. I don't think they will, since the barrier to entry is already quite high (e.g., sending email is more foreign to some than opening a GitHub issue, say).

So, I think that the suggestion above is a good one, since I believe we'd rather get some bad bug reports than no bug reports at all.

Thanks, Taylor

Previous: Martin ÅgrenNext: Martin Ågren
Message 4 of 12 in “git.txt: mention mailing list archive”
  1. git.txt: mention mailing list archiveMartin Ågren, Sep 19, 2018
  2. Junio C HamanoSep 20, 2018
  3. Martin ÅgrenSep 26, 2018
  4. Taylor BlauSep 26, 2018
  5. git.txt: mention mailing list archiveMartin Ågren, Sep 27, 2018
  6. Jonathan NiederSep 27, 2018
  7. Martin ÅgrenSep 27, 2018
  8. Junio C HamanoSep 28, 2018
  9. git doc: direct bug reporters to mailing list archive (Re: [PATCH v2] git.txt: mention mailing list archive)Jonathan Nieder, Sep 28, 2018
  10. Junio C HamanoSep 28, 2018
  11. Jonathan NiederSep 28, 2018
  12. Jonathan NiederSep 28, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.