git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: git@vger.kernel.org, "Jacob Abel" <jacobabel@nullpo.dev>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: ja/worktree-orphan (was What's cooking in git.git (Jan 2023, #04; Sat, 14))
Date: Sat, 14 Jan 2023 18:07:59 -0800	[thread overview]
Message-ID: <xmqqy1q4k0sg.fsf@gitster.g> (raw)
In-Reply-To: <11be1b0e-ee38-119f-1d80-cb818946116b@dunelm.org.uk> (Phillip Wood's message of "Sat, 14 Jan 2023 19:28:02 +0000")

Phillip Wood <phillip.wood123@gmail.com> writes:

> On 14/01/2023 08:36, Junio C Hamano wrote:
>> * ja/worktree-orphan (2023-01-13) 4 commits
>>   - worktree add: add hint to direct users towards --orphan
>>   - worktree add: add --orphan flag
>>   - worktree add: refactor opt exclusion tests
>>   - worktree add: include -B in usage docs
>>   'git worktree add' learned how to create a worktree based on an
>>   orphaned branch with `--orphan`.
>>   Will merge to 'next'.
>>   source: <20230109173227.29264-1-jacobabel@nullpo.dev>
>
> If possible it would be nice to clean up the ui before merging this, I
> think it would be quite a small change to the implementation. cf
> <e5aadd5d-9b85-4dc9-e9f7-117892b4b283@dunelm.org.uk>

Thanks.  Let's wait for and queue an updated one.

      reply	other threads:[~2023-01-15  2:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14  8:36 What's cooking in git.git (Jan 2023, #04; Sat, 14) Junio C Hamano
2023-01-14 12:48 ` Jeff King
2023-01-14 16:35   ` Junio C Hamano
2023-01-14 19:28 ` ja/worktree-orphan (was What's cooking in git.git (Jan 2023, #04; Sat, 14)) Phillip Wood
2023-01-15  2:07   ` Junio C Hamano [this message]

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=xmqqy1q4k0sg.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jacobabel@nullpo.dev \
    --cc=phillip.wood123@gmail.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).