git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: phillip.wood123@gmail.com
To: Caleb White <cdwhite3@pm.me>,
	phillip.wood@dunelm.org.uk, git@vger.kernel.org
Cc: Taylor Blau <me@ttaylorr.com>, Junio C Hamano <gitster@pobox.com>,
	Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH v2 3/5] worktree: add tests for worktrees with relative paths
Date: Tue, 29 Oct 2024 15:43:17 +0000	[thread overview]
Message-ID: <aeec08e2-29da-4e5e-8a73-7ed7e3a79177@gmail.com> (raw)
In-Reply-To: <D58DMTM9YPBE.8L5WT8ZNG1CU@pm.me>

On 29/10/2024 14:58, Caleb White wrote:
> On Tue Oct 29, 2024 at 9:52 AM CDT, Phillip Wood wrote:
>> Hi Caleb
>>
>> On 28/10/2024 19:09, Caleb White wrote:
>>> This patch expands the test coverage by adding cases that specifically
>>> handle relative paths. These tests verify correct behavior in a variety
>>> of operations, including: adding, listing, pruning, moving, and
>>> repairing worktrees with relative paths configured.
>>>
>>> This also adds a test case for reinitializing a repository that has
>>> relative worktrees.
>>
>> It's nice to see new tests being added. If they were added with the code
>> changes they test that would help reader understand the changes being
>> made I think.
> 
> I had received feedback that the original patch was too large, so I
> was trying to split it up into smaller, more digestible pieces. 

One way to do that would be to convert the "add", "move" and "repair" 
subcommands in separate patches changing option handling and appropriate 
tests in each one rather than changing all subcommands and their tests 
at once.

Best Wishes

Phillip

I could
> go either way so it's really what the reviewers would prefer.
> 
> Best,
> Caleb
> 


  reply	other threads:[~2024-10-29 15:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 19:09 [PATCH v2 0/5] Allow relative worktree linking to be configured by the user Caleb White
2024-10-28 19:09 ` [PATCH v2 1/5] worktree: add CLI/config options for relative path linking Caleb White
2024-10-29 14:52   ` Phillip Wood
2024-10-30  5:27     ` Caleb White
2024-10-30 20:16       ` Taylor Blau
2024-10-30 20:21         ` Caleb White
2024-10-30 20:30           ` phillip.wood123
2024-10-30 20:36             ` Caleb White
2024-10-29 18:42   ` Taylor Blau
2024-10-30  5:07     ` Caleb White
2024-10-28 19:09 ` [PATCH v2 2/5] worktree: add `write_worktree_linking_files` function Caleb White
2024-10-29 14:52   ` Phillip Wood
2024-10-29 22:55     ` Taylor Blau
2024-10-30  5:38       ` Caleb White
2024-10-30  5:30     ` Caleb White
2024-10-28 19:09 ` [PATCH v2 3/5] worktree: add tests for worktrees with relative paths Caleb White
2024-10-29 14:52   ` Phillip Wood
2024-10-29 14:58     ` Caleb White
2024-10-29 15:43       ` phillip.wood123 [this message]
2024-10-30  5:10         ` Caleb White
2024-10-29 23:00   ` Taylor Blau
2024-10-30  4:16     ` Caleb White
2024-10-28 19:10 ` [PATCH v2 4/5] setup: correctly reinitialize repository version Caleb White
2024-10-28 19:10 ` [PATCH v2 5/5] worktree: add `relativeWorktrees` extension Caleb White
2024-10-29 14:55 ` [PATCH v2 0/5] Allow relative worktree linking to be configured by the user Phillip Wood
2024-10-30  5:13   ` 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=aeec08e2-29da-4e5e-8a73-7ed7e3a79177@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).