git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2025, #04; Fri, 10)
Date: Mon, 13 Oct 2025 08:28:05 -0700	[thread overview]
Message-ID: <xmqqv7ki3jp6.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cQOAU3J4qmdtjwRCRkwqpO2FfgDThLt6Yoxdx9T6bhTOA@mail.gmail.com> (Eric Sunshine's message of "Sat, 11 Oct 2025 01:23:55 -0400")

Eric Sunshine <sunshine@sunshineco.com> writes:

> On Fri, Oct 10, 2025 at 8:00 PM Junio C Hamano <gitster@pobox.com> wrote:
>> * ms/doc-worktree-side-by-side (2025-10-10) 2 commits
>>  - doc: git-worktree: Add side by side branch checkout example
>>  - doc: git-worktree: Link to examples
>>
>>  Document "git worktree add" and use of out-of-tree worktrees with
>>  examples.
>>
>>  Will merge to 'next'?
>>  source: <a203b35538847f3c9358a5ae26fb4ebea5734cfc.1759420102.git.msuchanek@suse.de>
>
> I'd prefer that this not be merged to 'next' in its present form since
> I think the first patch either needs significantly more justification
> or ought to be dropped altogether[1], and because the second patch
> still needs a good deal of work[2].
>
> [1]: https://lore.kernel.org/git/CAPig+cQRHp7A=gtSkrVS4_EvZ9PyqBOdGGHcEajfLPE=qU4uDQ@mail.gmail.com/
> [2]: https://lore.kernel.org/git/CAPig+cSNesf0UwS4=Bxe-Qn+G9y3YYPyOK+7y3q8QJk+o7jaVg@mail.gmail.com/

Let me watch from the sidelines how the discussion goes.

Thanks.

  reply	other threads:[~2025-10-13 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-11  0:00 What's cooking in git.git (Oct 2025, #04; Fri, 10) Junio C Hamano
2025-10-11  5:23 ` Eric Sunshine
2025-10-13 15:28   ` Junio C Hamano [this message]
2025-10-11 11:00 ` Patrick Steinhardt
2025-10-13 14:07   ` Junio C Hamano
2025-10-11 14:35 ` D. Ben Knoble
2025-10-11 17:14   ` Junio C Hamano
2025-10-12 18:02     ` Ben Knoble

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=xmqqv7ki3jp6.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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).