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

Re: [PATCH v2 0/5] mh: worktree-related doc fixes

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Jul 24, 2015, 00:10 UTC
Message-ID
<CAPig+cRLZiLSrMDiPp9ZJ1RKELSEKqVc0K2h4CvnvXNk5t7aBw@mail.gmail.com>
In-Reply-To
<55AD146D.3080509@alum.mit.edu>
On Mon, Jul 20, 2015 at 11:31 AM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
Show 14 quoted lines
> On 07/19/2015 10:29 PM, Eric Sunshine wrote:
>> This re-roll of Michael Haggerty's worktree-related documentation
>> tweaks[1] takes my review comments into account and adds one new patch.
>
> Thanks for separating the wheat from the chaff. I'm still traveling,
> which I'll claim as an excuse for my poor responsiveness.
>
> All of your changes look good.
>
> I was wondering one thing: is there a value like "never" or "false" to
> which "gc.worktreepruneexpire" can be set to turn off pruning entirely?
> If so, it might be nice to mention it in the config manpage. Similarly
> for the other expiration grace time settings.
> But it's definitely not a blocker.

I browsed the code for the various "expire" settings, and it appears that they all accept and respect "now" and "never", as well, so I'll put together a patch as suggested.

Previous: Michael HaggertyNext: Junio C Hamano
Message 8 of 9 in “mh: worktree-related doc fixes”
  1. 0/5 mh: worktree-related doc fixesEric Sunshine, Jul 20, 2015
  2. 1/5 Documentation/git-worktree: consistently use term "linked working tree"Eric Sunshine, Jul 20, 2015
  3. 2/5 Documentation/git-worktree: fix incorrect reference to file "locked"Eric Sunshine, Jul 20, 2015
  4. 3/5 Documentation/config: fix stale "git prune --worktree" referenceEric Sunshine, Jul 20, 2015
  5. 4/5 Documentation/git-worktree: wordsmith worktree-related manpagesEric Sunshine, Jul 20, 2015
  6. 5/5 config: rename "gc.pruneWorktreesExpire" to "gc.worktreePruneExpire"Eric Sunshine, Jul 20, 2015
  7. Michael HaggertyJul 20, 2015
  8. Eric SunshineJul 24, 2015
  9. Junio C HamanoJul 24, 2015

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.