Jeff King <p...@peff.net> writes: > FWIW, as the person who wrote that section, I think that is a good > addition. We do have a link to Simon Tatham's bug-reporting guide, but > this is a good place to put project-specific advice. > > In addition to "try it on next" you may want to also mention "try it on > the latest version of git". That is another frequently given pointer to > bug reporters. Trying "next" is obviously a superset, but I suspect > trying a released version may be an easier first step for some people.
Yes, definitely. I agree that testing with the latest released version would typically be much easier to end users than building from the source. It would reduce the need for "Ah, that's ancient issue, we know it was fixed a few releases ago." responses by us; I do not recall many of such responses in the recent history on the list, though. For the ones who are more into the spirit of helping each other who can build from the source to help us even more, checking 'master' and finding regressions before it gets too late is a very good thing. Checking 'next' and confirming an upcoming fix is equally valuable. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
