From: Matt McCutchen <matt@mattmccutchen.net>
To: git@vger.kernel.org
Subject: [PATCH] git.txt: encourage bug reporters to test recent versions
Date: Mon, 8 Feb 2016 19:34:25 -0500 [thread overview]
Message-ID: <1455048415.2511.200.camel@mattmccutchen.net> (raw)
In-Reply-To: <20160208135607.GB27054@sigill.intra.peff.net>
Specifically, the latest released version or the "next" branch, as
reporters are willing. This is based on:
http://marc.info/?l=git&m=145496979420513&w=2
Signed-off-by: Matt McCutchen <matt@mattmccutchen.net>
---
Documentation/git.txt | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index d987ad2..1a148bc 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -1226,7 +1226,11 @@ Reporting Bugs
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.
+subscribed to the list to send a message there. You can help us out by
+attempting to reproduce the bug in the latest released version of git,
+or if you're willing to build git from source, the `next` branch.
+Sometimes an attempted fix may be pending in this branch, in which case
+your feedback as to whether the fix worked for you will be appreciated.
SEE ALSO
--------
--
2.5.0
prev parent reply other threads:[~2016-02-09 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 20:12 update_linked_gitdir writes relative path to .git/worktrees/<id>/gitdir Matt McCutchen
2016-02-07 23:56 ` Junio C Hamano
2016-02-08 1:04 ` Matt McCutchen
2016-02-08 4:56 ` Duy Nguyen
2016-02-08 13:56 ` Jeff King
2016-02-08 22:16 ` Junio C Hamano
2016-02-09 20:05 ` Matt McCutchen
2016-02-09 21:02 ` Junio C Hamano
2016-02-09 20:30 ` Making the "Note from the maintainer" information discoverable Matt McCutchen
2016-02-09 0:34 ` Matt McCutchen [this message]
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=1455048415.2511.200.camel@mattmccutchen.net \
--to=matt@mattmccutchen.net \
--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).