Re: [PATCH v4 0/8] Allow relative worktree linking to be configured by the user

[Caleb White <cdwhite3@pm.me>]

On Fri Nov 1, 2024 at 2:14 AM CDT, Junio C Hamano wrote:
> Caleb White <cdwhite3@pm.me> writes:
>
>> The base for this patch series is obtained by applying the following
>> patch onto 6a11438f43:
>> - cw/config-extensions topic (doc: consolidate extensions in git-config
>>   documentation, 2024-10-22, <20241021-cleanup-extension-docs-v1-1-ab02cece3132@pm.me>)
>
> I am slowing getting back to speed, but with the above I noticed two
> things.

Welcome back! I hope you had a good break :).

>  - Do not encourage people to _apply_ random patches before your
>    series when the official tree has the same patches.  In this
>    case, you even know the branch the official tree uses
>    (i.e. cw/config-extensions), so tell readers to _merge_ the
>    topic before applying your series instead.

Ah, my apologies. I will make sure to do that in the future. When
I first added this note, a topic branch[1] had not been created yet and
I forgot to update it when it was.

>  - The notes/amlog I snarfed from the broken-out repository of
>    Taylor does not seem to record the message ID
>    <20241021-cleanup-extension-docs-v1-1-ab02cece3132@pm.me> Perhaps
>    I was looking at a wrong repository?

Hmm, I'm not sure. Here's the latest update in the What's Cooking report:

    * cw/config-extensions (2024-10-22) 1 commit
     (merged to 'next' on 2024-10-30 at 875fa0b619)
     + doc: consolidate extensions in git-config documentation
     (this branch is used by cw/worktree-extension.)

     Centralize documentation for repository extensions into a single place.

     Will merge to 'master'?
     source: <20241021-cleanup-extension-docs-v1-1-ab02cece3132@pm.me>

Best,

[1]: https://github.com/ttaylorr/git/tree/cw/config-extensions