git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Martin Ågren" <martin.agren@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>,
	"Taylor Blau" <me@ttaylorr.com>
Subject: Re: [PATCH] git doc: direct bug reporters to mailing list archive (Re: [PATCH v2] git.txt: mention mailing list archive)
Date: Fri, 28 Sep 2018 15:27:30 -0700	[thread overview]
Message-ID: <xmqqd0sx9s19.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180928212049.GD193055@aiede.svl.corp.google.com> (Jonathan Nieder's message of "Fri, 28 Sep 2018 14:20:49 -0700")

Jonathan Nieder <jrnieder@gmail.com> writes:

> My experience is that bug reporters are very sensitive to hints the
> project gives about what kind of bugs they want to receive.  I'd
> rather make use of that lesson now instead of waiting to relearn it in
> the wild.  Here goes.

OK.  This unfortunately came a bit too late for today's integration
cycle, so I'll leave this in my inbox and replace what is queued 
with it later.

Unless there is another one to supersede this proposal comes before
that happens, that is.

Thanks.


  reply	other threads:[~2018-09-28 22:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 16:43 [PATCH] git.txt: mention mailing list archive Martin Ågren
2018-09-20 19:07 ` Junio C Hamano
2018-09-26  8:05   ` Martin Ågren
2018-09-26 13:47     ` Taylor Blau
2018-09-27  5:50       ` [PATCH v2] " Martin Ågren
2018-09-27  6:37         ` Jonathan Nieder
2018-09-27 10:35           ` Martin Ågren
2018-09-28 16:56             ` Junio C Hamano
2018-09-28 21:20               ` [PATCH] git doc: direct bug reporters to mailing list archive (Re: [PATCH v2] git.txt: mention mailing list archive) Jonathan Nieder
2018-09-28 22:27                 ` Junio C Hamano [this message]
2018-09-28 22:29                   ` Jonathan Nieder
2018-09-28 23:09                     ` Jonathan Nieder

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=xmqqd0sx9s19.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=martin.agren@gmail.com \
    --cc=me@ttaylorr.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).