git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: Caleb White <cdwhite3@pm.me>, git@vger.kernel.org
Cc: Taylor Blau <me@ttaylorr.com>, Junio C Hamano <gitster@pobox.com>,
	Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH v6 0/8] Allow relative worktree linking to be configured by the user
Date: Mon, 2 Dec 2024 14:57:38 +0000	[thread overview]
Message-ID: <103c7a4d-a74b-4381-a9c7-33a89d5db192@gmail.com> (raw)
In-Reply-To: <20241129-wt_relative_options-v6-0-44e4e0bec8c3@pm.me>

Hi Caleb

On 29/11/2024 22:22, Caleb White wrote:
> Changes in v6:
> - Re-add test for extensions.relativeworktrees config setting
> - Link to v5: https://lore.kernel.org/r/20241125-wt_relative_options-v5-0-356d122ff3db@pm.me

The range-diff below looks good, thanks for working on this
I think it's ready for next

Best Wishes

Phillip

1:  0986f98022 = 1:  d897f2c16d setup: correctly reinitialize repository version
2:  c36e1a59fa = 2:  1860ba1a2a worktree: add `relativeWorktrees` extension
3:  5b19b63040 = 3:  5976310916 worktree: refactor infer_backlink return
4:  ec143ae00e = 4:  4dac9e3c01 worktree: add `write_worktree_linking_files()` function
5:  237206b08f ! 5:  b7016344f1 worktree: add relative cli/config options to `add` command
     @@ t/t2400-worktree-add.sh: test_expect_success '"add" with initialized submodule,
      +  git init repo &&
      +  git -C repo commit --allow-empty -m base &&
      +  git -C repo worktree add --relative-paths ./foo &&
     -+  test_cmp_config -C repo 1 core.repositoryformatversion
     ++  test_cmp_config -C repo 1 core.repositoryformatversion &&
     ++  test_cmp_config -C repo true extensions.relativeworktrees
      +'
      +
       test_done
6:  8e4307f520 = 6:  298d2917e2 worktree: add relative cli/config options to `move` command
7:  4f951f4088 = 7:  e6df1ee2c1 worktree: add relative cli/config options to `repair` command
8:  28eb7f66b2 = 8:  2037ca85ad worktree: refactor `repair_worktree_after_gitdir_move()`

> Changes in v5:
> - Added docs to `--relative-paths` option.
> - Added test coverage for `repair_worktrees()` and relative paths.
> - Move `strbuf_reset` call in `infer_backlink()`.
> - Cleaned up tests.
> - Slight stylistic changes.
> - Tweaked commit messages.
> - Updated base to 090d24e9af.
> - Link to v4: https://lore.kernel.org/r/20241031-wt_relative_options-v4-0-07a3dc0f02a3@pm.me
> Changes in v4:
> - Fixed failing test in ci
> - Link to v3: https://lore.kernel.org/r/20241031-wt_relative_options-v3-0-3e44ccdf64e6@pm.me
> Changes in v3:
> - Split patches into smaller edits.
> - Moved tests into the patches with the relevant code changes.
> - Removed global `use_relative_paths` and instead pass parameter to functions.
> - Changed `infer_backlink` return type from `int` to `ssize_t`.
> - Updated `worktree.useRelativePaths` and `--relative-paths` descriptions.
> - Reordered patches
> - Link to v2: https://lore.kernel.org/r/20241028-wt_relative_options-v2-0-33a5021bd7bb@pm.me
> Changes in v2:
> - Fixed a bug where repositories with valid extensions would be downgraded
>    to v0 during reinitialization, causing future operations to fail.
> - Split patch [1/2] into three separate patches.
> - Updated cover letter and commit messages.
> - Updated documentation wording.
> - Link to v1: https://lore.kernel.org/r/20241025-wt_relative_options-v1-0-c3005df76bf9@pm.me
> 
> ---
> Caleb White (8):
>        setup: correctly reinitialize repository version
>        worktree: add `relativeWorktrees` extension
>        worktree: refactor infer_backlink return
>        worktree: add `write_worktree_linking_files()` function
>        worktree: add relative cli/config options to `add` command
>        worktree: add relative cli/config options to `move` command
>        worktree: add relative cli/config options to `repair` command
>        worktree: refactor `repair_worktree_after_gitdir_move()`
> 
>   Documentation/config/extensions.txt |   6 ++
>   Documentation/config/worktree.txt   |  10 +++
>   Documentation/git-worktree.txt      |   8 ++
>   builtin/worktree.c                  |  29 ++++---
>   repository.c                        |   1 +
>   repository.h                        |   1 +
>   setup.c                             |  39 ++++++---
>   setup.h                             |   1 +
>   t/t0001-init.sh                     |  22 ++++-
>   t/t2400-worktree-add.sh             |  46 +++++++++++
>   t/t2401-worktree-prune.sh           |   3 +-
>   t/t2402-worktree-list.sh            |  22 +++++
>   t/t2403-worktree-move.sh            |  25 ++++++
>   t/t2406-worktree-repair.sh          |  39 +++++++++
>   t/t2408-worktree-relative.sh        |  39 ---------
>   t/t5504-fetch-receive-strict.sh     |   6 +-
>   worktree.c                          | 157 ++++++++++++++++++++----------------
>   worktree.h                          |  22 ++++-
>   18 files changed, 334 insertions(+), 142 deletions(-)
> ---
> base-commit: 090d24e9af6e9f59c3f7bee97c42bb1ae3c7f559
> change-id: 20241025-wt_relative_options-afa41987bc32
> 
> Best regards,


  parent reply	other threads:[~2024-12-02 14:57 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01  4:38 [PATCH v4 0/8] Allow relative worktree linking to be configured by the user Caleb White
2024-11-01  4:38 ` [PATCH v4 1/8] setup: correctly reinitialize repository version Caleb White
2024-11-01  4:38 ` [PATCH v4 2/8] worktree: add `relativeWorktrees` extension Caleb White
2024-11-19 15:07   ` Phillip Wood
2024-11-20  5:13     ` Caleb White
2024-11-22 16:44       ` Phillip Wood
2024-11-22 19:27         ` Caleb White
2024-11-01  4:38 ` [PATCH v4 3/8] worktree: refactor infer_backlink return Caleb White
2024-11-19 15:08   ` Phillip Wood
2024-11-20  5:20     ` Caleb White
2024-11-22 16:44       ` Phillip Wood
2024-11-22 19:26         ` Caleb White
2024-11-01  4:38 ` [PATCH v4 4/8] worktree: add `write_worktree_linking_files()` function Caleb White
2024-11-01  4:38 ` [PATCH v4 5/8] worktree: add relative cli/config options to `add` command Caleb White
2024-11-19 15:07   ` Phillip Wood
2024-11-20  5:01     ` Caleb White
2024-11-22 16:44       ` phillip.wood123
2024-11-23  4:40         ` Caleb White
2024-11-01  4:38 ` [PATCH v4 6/8] worktree: add relative cli/config options to `move` command Caleb White
2024-11-22 15:55   ` Phillip Wood
2024-11-23  4:11     ` Caleb White
2024-11-01  4:38 ` [PATCH v4 7/8] worktree: add relative cli/config options to `repair` command Caleb White
2024-11-22 15:55   ` Phillip Wood
2024-11-23  5:41     ` Caleb White
2024-11-24 19:27       ` phillip.wood123
2024-11-26  0:00         ` Caleb White
2024-11-01  4:39 ` [PATCH v4 8/8] worktree: refactor `repair_worktree_after_gitdir_move()` Caleb White
2024-11-22 15:58   ` Phillip Wood
2024-11-23  4:36     ` Caleb White
2024-11-01  7:14 ` [PATCH v4 0/8] Allow relative worktree linking to be configured by the user Junio C Hamano
2024-11-01 13:18   ` Caleb White
2024-11-02 10:09     ` Junio C Hamano
2024-11-02 14:36   ` Kristoffer Haugsbakk
2024-11-22 15:57 ` Phillip Wood
2024-11-23  5:45   ` Caleb White
2024-11-26  1:51 ` [PATCH v5 " Caleb White
2024-11-26  1:51   ` [PATCH v5 1/8] setup: correctly reinitialize repository version Caleb White
2024-11-26  1:51   ` [PATCH v5 2/8] worktree: add `relativeWorktrees` extension Caleb White
2024-11-26  1:51   ` [PATCH v5 3/8] worktree: refactor infer_backlink return Caleb White
2024-11-26  1:51   ` [PATCH v5 4/8] worktree: add `write_worktree_linking_files()` function Caleb White
2024-11-26  1:52   ` [PATCH v5 5/8] worktree: add relative cli/config options to `add` command Caleb White
2024-11-26  1:52   ` [PATCH v5 6/8] worktree: add relative cli/config options to `move` command Caleb White
2024-11-26  1:52   ` [PATCH v5 7/8] worktree: add relative cli/config options to `repair` command Caleb White
2024-11-26  1:52   ` [PATCH v5 8/8] worktree: refactor `repair_worktree_after_gitdir_move()` Caleb White
2024-11-26  6:18   ` [PATCH v5 0/8] Allow relative worktree linking to be configured by the user Junio C Hamano
2024-11-26 17:02     ` Caleb White
2024-11-28 14:44   ` Phillip Wood
2024-11-28 17:58     ` Caleb White
2024-11-29 22:22   ` [PATCH v6 " Caleb White
2024-11-29 22:22     ` [PATCH v6 1/8] setup: correctly reinitialize repository version Caleb White
2024-11-29 22:22     ` [PATCH v6 2/8] worktree: add `relativeWorktrees` extension Caleb White
2024-11-29 22:22     ` [PATCH v6 3/8] worktree: refactor infer_backlink return Caleb White
2024-11-29 22:22     ` [PATCH v6 4/8] worktree: add `write_worktree_linking_files()` function Caleb White
2024-11-29 22:22     ` [PATCH v6 5/8] worktree: add relative cli/config options to `add` command Caleb White
2024-11-29 22:23     ` [PATCH v6 6/8] worktree: add relative cli/config options to `move` command Caleb White
2024-11-29 22:23     ` [PATCH v6 7/8] worktree: add relative cli/config options to `repair` command Caleb White
2024-11-29 22:23     ` [PATCH v6 8/8] worktree: refactor `repair_worktree_after_gitdir_move()` Caleb White
2024-12-02 14:57     ` Phillip Wood [this message]
2024-12-03  4:54       ` [PATCH v6 0/8] Allow relative worktree linking to be configured by the user Junio C Hamano
2024-12-03  5:21         ` Caleb White

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=103c7a4d-a74b-4381-a9c7-33a89d5db192@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=cdwhite3@pm.me \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.com \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=sunshine@sunshineco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).