From: Phillip Wood <phillip.wood123@gmail.com>
To: Karthik Nayak <karthik.188@gmail.com>,
Phillip Wood <phillip.wood@dunelm.org.uk>,
git@vger.kernel.org
Cc: Shreyansh Paliwal <shreyanshpaliwalcmsmn@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH 1/2] wt-status: avoid passing NULL worktree
Date: Wed, 18 Feb 2026 14:19:56 +0000 [thread overview]
Message-ID: <d881edeb-d73b-43ba-bdb3-1b664e1cb882@gmail.com> (raw)
In-Reply-To: <CAOLa=ZQKLqFn4w3s7PD87FZ_120gohoqKX5c3uLKo2vASsbxfA@mail.gmail.com>
On 17/02/2026 17:46, Karthik Nayak wrote:
> Phillip Wood <phillip.wood123@gmail.com> writes:
>> From: Phillip Wood <phillip.wood@dunelm.org.uk>
>>
>> This updates the only callers that pass a NULL worktree to
>> worktree_git_path().
>>
>
> I was thinking surely there must be other places where we also pass NULL
> for worktree, but doesn't seem like there are any such instances.
Yes, I was pleasantly surprised there weren't more sites to convert.
>> +struct worktree *get_worktree_from_repository(struct repository *repo)
>> +{
>> + struct worktree *wt = xcalloc(1, sizeof(*wt));
>> + char *gitdir = absolute_pathdup(repo->gitdir);
>> + char *commondir = absolute_pathdup(repo->commondir);
>> +
>> + wt->repo = repo;
>> + if (repo->worktree)
>> + wt->path = absolute_pathdup(repo->worktree);
>
> Shouldn't this always be set? I guess my question is, will
> `repo->worktree` ever be NULL?
Oh, wt->path should never be NULL. repo->worktree is NULL in bare
repositories but then we should use repo->gitdir as the worktree path.
>> + wt->is_bare = !!repo->worktree;
>> + if (fspathcmp(gitdir, commondir))
>> + wt->id = xstrdup(find_last_dir_sep(commondir) + 1);
>
> So here we continue to treat NULL as the main worktree. Okay.
>
>> + wt->is_current = is_current_worktree(wt);
>
> Since we're getting the worktree from the repo, shouldn't this be
> 'true'?
That's what I thought initially. However is_current_worktree() compares
"repo->gitdir" to "the_repository->gitdir" so the "current" worktree is
the one that the process was started in, which is not necessarily the
same as the one matching "wt->repo->gitdir". It's possible that we will
want to change that definition in the future but I opted to make this
function consistent with the status quo.
>> -/*
>> +/* Construct a struct worktree from a struct repository */
>> +struct worktree *get_worktree_from_repository(struct repository *repo);
>> +
>> + /*
>
> Nit: extra space?
Good spot I'll fix it
Thanks for the review
Phillip
next prev parent reply other threads:[~2026-02-18 14:19 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 11:59 [RFC][PATCH 0/2] worktree: change representation and usage of primary worktree Shreyansh Paliwal
2026-02-13 11:59 ` [RFC][PATCH 1/2] worktree: represent the primary worktree with '/' instead of NULL Shreyansh Paliwal
2026-02-13 21:35 ` Junio C Hamano
2026-02-14 9:54 ` Shreyansh Paliwal
2026-02-13 11:59 ` [RFC][PATCH 2/2] worktree: stop passing NULL as primary worktree Shreyansh Paliwal
2026-02-13 22:29 ` Junio C Hamano
2026-02-14 9:59 ` Shreyansh Paliwal
2026-02-14 14:30 ` Phillip Wood
2026-02-14 15:34 ` Junio C Hamano
2026-02-15 8:56 ` Shreyansh Paliwal
2026-02-16 16:18 ` Phillip Wood
2026-02-17 5:21 ` Junio C Hamano
2026-02-17 10:09 ` Shreyansh Paliwal
2026-02-16 16:18 ` [PATCH 0/2] worktree_git_path(): remove repository argument Phillip Wood
2026-02-16 16:18 ` [PATCH 1/2] wt-status: avoid passing NULL worktree Phillip Wood
2026-02-17 9:23 ` Phillip Wood
2026-02-17 10:18 ` Shreyansh Paliwal
2026-02-17 15:20 ` Phillip Wood
2026-02-17 16:38 ` Shreyansh Paliwal
2026-02-17 18:29 ` Junio C Hamano
2026-02-17 17:46 ` Karthik Nayak
2026-02-18 14:19 ` Phillip Wood [this message]
2026-02-17 18:47 ` Junio C Hamano
2026-02-18 14:18 ` Phillip Wood
2026-02-16 16:18 ` [PATCH 2/2] path: remove repository argument from worktree_git_path() Phillip Wood
2026-02-17 17:48 ` Karthik Nayak
2026-02-17 10:12 ` [PATCH 0/2] worktree_git_path(): remove repository argument Shreyansh Paliwal
2026-02-17 15:22 ` Phillip Wood
2026-02-17 16:45 ` Shreyansh Paliwal
2026-02-19 14:26 ` [PATCH v2 " Phillip Wood
2026-02-19 14:26 ` [PATCH v2 1/2] wt-status: avoid passing NULL worktree Phillip Wood
2026-02-19 19:30 ` Junio C Hamano
2026-02-19 20:37 ` Junio C Hamano
2026-02-25 16:39 ` Phillip Wood
2026-02-25 17:11 ` Junio C Hamano
2026-02-26 16:09 ` Phillip Wood
2026-02-26 16:15 ` Junio C Hamano
2026-02-19 14:26 ` [PATCH v2 2/2] path: remove repository argument from worktree_git_path() Phillip Wood
2026-02-19 19:34 ` Junio C Hamano
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=d881edeb-d73b-43ba-bdb3-1b664e1cb882@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=shreyanshpaliwalcmsmn@gmail.com \
--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