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

Re: update_linked_gitdir writes relative path to .git/worktrees/<id>/gitdir

From
Matt McCutchen <matt@mattmccutchen.net>
Date
Feb 9, 2016, 20:05 UTC
Message-ID
<1455048354.2511.199.camel@mattmccutchen.net>
In-Reply-To
<xmqqziva6e6e.fsf@gitster.mtv.corp.google.com>
On Mon, 2016-02-08 at 14:16 -0800, Junio C Hamano wrote:
Show 24 quoted lines
> Jeff King <peff@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.

OK, so this testing is an encouragement, not an expectation per se, even if bug reports may be less likely to get attention without it (I'm not familiar with the degree to which this may have been the case recently).  See my revised proposed text here:

https://github.com/git/git-scm.com/pull/676/files
I'll send an analogous patch for the git(1) man page in a moment.

I left a mention of providing feedback on pending fixes but thought it would be too much to go into the details of how to identify whether there is a pending fix.  Is this sensible?

Matt
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 10 in “update_linked_gitdir writes relative path to .git/worktrees/<id>/gitdir”
  1. Matt McCutchenFeb 6, 2016
  2. Junio C HamanoFeb 7, 2016
  3. Matt McCutchenFeb 8, 2016
  4. Duy NguyenFeb 8, 2016
  5. Jeff KingFeb 8, 2016
  6. Junio C HamanoFeb 8, 2016
  7. Matt McCutchenFeb 9, 2016
  8. Junio C HamanoFeb 9, 2016
  9. Making the "Note from the maintainer" information discoverableMatt McCutchen, Feb 9, 2016
  10. git.txt: encourage bug reporters to test recent versionsMatt McCutchen, Feb 9, 2016

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.