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

Re: [PATCH v3 0/5] Optionally link worktrees with relative paths

From
Taylor Blau <me@ttaylorr.com>
Date
Oct 25, 2024, 21:38 UTC
Message-ID
<ZxwPwfJnEJ8C/rkz@nand.local>
In-Reply-To
<D5572ICCKQXT.3UQ8AJ2GSUZIP@pm.me>
On Fri, Oct 25, 2024 at 09:11:30PM +0000, Caleb White wrote:
> Ah, I must've missed that---I was in the process of working on v4 and
> didn't realize that it had already been merged to master.
>
> I'll send a new round based on the current tip of master.
Thanks.

Looking at the dates, I should have held the existing round in 'next' for a few days longer. But I figured that the existing v3 was already in a good state, and hadn't heard otherwise since the original thread[1] was quiet.

Thanks, Taylor

[1]: https://lore.kernel.org/git/20241007-wt_relative_paths-v3-0-622cf18c45eb@pm.me/
Previous: Caleb WhiteNext: Caleb White
Message 10 of 11 in “Optionally link worktrees with relative paths”
  1. 0/5 Optionally link worktrees with relative pathsCaleb White, Oct 25, 2024
  2. 1/5 worktree: refactor infer_backlink() to use strbuf*Caleb White, Oct 25, 2024
  3. 2/5 worktree: support worktrees linked with relative pathsCaleb White, Oct 25, 2024
  4. 4/5 worktree: add test for path handling in linked worktreesCaleb White, Oct 25, 2024
  5. 3/5 worktree: optionally link worktrees with relative pathsCaleb White, Oct 25, 2024
  6. 5/5 worktree: add `relativeWorktrees` extensionCaleb White, Oct 25, 2024
  7. Caleb WhiteOct 25, 2024
  8. Taylor BlauOct 25, 2024
  9. Caleb WhiteOct 25, 2024
  10. Taylor BlauOct 25, 2024
  11. Caleb WhiteOct 25, 2024

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.