Re: update_linked_gitdir writes relative path to .git/worktrees/<id>/gitdir
- From
Jeff King <peff@peff.net>
- Date
- Feb 8, 2016, 13:56 UTC
- Message-ID
- <20160208135607.GB27054@sigill.intra.peff.net>
- In-Reply-To
- <1454893478.2511.5.camel@mattmccutchen.net>
On Sun, Feb 07, 2016 at 08:04:38PM -0500, Matt McCutchen wrote:
Show 15 quoted lines
> > it is very much > > appreciated when reporting bugs people check if a presumed fix is > > already cooking in 'next', try it to verify if it really fixes their > > problem, and send in a "OK fix is good" / "No that does not fix my > > case"? > > Sorry to waste your time. This wasn't documented where I looked, > namely the "Bug Reporting" section on http://git-scm.com/community . > Here's a straw-man proposed update to that page: > > https://github.com/mattmccutchen/git-scm.com/compare/master...bug-reporting-next > > If you like it, I will submit it as a pull request. I can propose a > similar update to the "REPORTING BUGS" section of the git(1) man page > if you like.
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.
-Peff