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:05 UTC
Message-ID
<ZxwIEcUKMELmxeMh@nand.local>
In-Reply-To
<20241025-wt_relative_paths-v3-0-8860a5321c01@pm.me>
On Fri, Oct 25, 2024 at 08:57:17PM +0000, Caleb White wrote:
Show 6 quoted lines
> Caleb White (5):
>       worktree: refactor infer_backlink() to use strbuf*
>       worktree: support worktrees linked with relative paths
>       worktree: optionally link worktrees with relative paths
>       worktree: add test for path handling in linked worktrees
>       worktree: add `relativeWorktrees` extension

The previous round was already merged to 'master' a few days ago[1], after merging it to 'next' and saying so in this[2] WC report.

I'm not sure if you intended to send this series as a follow-up to the state that was already merged to 'master', or if you had intended to send a new round of changes not knowing it had already been merged.

In either case, can you please send a new round based on the current tip of 'master'?

Thanks, Taylor

[1]: 8e08668322 (Merge branch 'cw/worktree-relative', 2024-10-22). [2]: https://lore.kernel.org/git/ZxLI06smvMuf%2FcT2@nand.local/

Previous: Caleb WhiteNext: Caleb White
Message 8 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.