From: Caleb White <cdwhite3@pm.me>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Phillip Wood <phillip.wood123@gmail.com>,
shejialuo <shejialuo@gmail.com>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Subject: Re: [PATCH 1/2] worktree: add CLI/config options for relative path linking
Date: Mon, 28 Oct 2024 18:50:12 +0000 [thread overview]
Message-ID: <D57NXXVF7BEW.2JASTW8099JUI@pm.me> (raw)
In-Reply-To: <Zx/B3caIgAeAv6Kz@nand.local>
On Mon Oct 28, 2024 at 11:54 AM CDT, Taylor Blau wrote:
> On Mon, Oct 28, 2024 at 04:35:22PM +0000, Caleb White wrote:
>> Thanks for catching this, the issue is that there's a bug in the
>> `initialize_repository_version()` function when reinitializing a
>> repository---the function doesn't check if there are other extensions
>> in use before downgrading the repository version to 0.
>>
>> This is a rare edge case, but I'll work on a fix.
>
> I am confused... are you saying t0001.46 is flaky? I don't think that
> it is, as it fails consistently for me with your patches applied when
> ran in a loop.
No, the test is not flaky. Adding the extension just revealed a bug in
the code that was not caught by the test suite. I've fixed the bug and
will push v2 here shortly.
> I am definitely guilty of having sent broken patches to the list before
> that fail CI, usually when I have amended something I thought was
> trivial after already running the test suite on all patches, only to
> realize that it wasn't trivial after all and instead broken something.
>
> But please do be careful to thoroughly vet your patches before sending
> them to the list, as this sort of breakage can be disruptive.
The test suite was passing, I must've just forgotten to execute this
again test after I added the extension. I'll be more careful in the
future.
Best,
Caleb
next prev parent reply other threads:[~2024-10-28 18:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 22:29 [PATCH 0/2] Allow relative worktree linking to be configured by the user Caleb White
2024-10-25 22:29 ` [PATCH 1/2] worktree: add CLI/config options for relative path linking Caleb White
2024-10-28 0:17 ` Taylor Blau
2024-10-28 0:34 ` Taylor Blau
2024-10-28 16:35 ` Caleb White
2024-10-28 16:54 ` Taylor Blau
2024-10-28 18:50 ` Caleb White [this message]
2024-10-28 1:16 ` Caleb White
2024-10-25 22:29 ` [PATCH 2/2] worktree: add `relativeWorktrees` extension Caleb White
2024-10-28 0:20 ` Taylor Blau
2024-10-28 1:14 ` Caleb White
2024-10-28 17:08 ` Taylor Blau
2024-10-28 19:00 ` Caleb White
2024-10-28 23:36 ` Taylor Blau
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=D57NXXVF7BEW.2JASTW8099JUI@pm.me \
--to=cdwhite3@pm.me \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=me@ttaylorr.com \
--cc=phillip.wood123@gmail.com \
--cc=shejialuo@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;
as well as URLs for NNTP newsgroup(s).