All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Taylor Blau <me@ttaylorr.com>,
	git@vger.kernel.org, Jacob Abel <jacobabel@nullpo.dev>
Subject: Re: What's cooking in git.git (Nov 2022, #03; Mon, 14)
Date: Tue, 15 Nov 2022 21:04:34 -0500	[thread overview]
Message-ID: <Y3RFMrhgVYLR6nZ4@nand.local> (raw)
In-Reply-To: <CAPig+cSKaW0ejeVgS7XEphMibdmExxO_T+xjMo6My5SAfwou_Q@mail.gmail.com>

On Tue, Nov 15, 2022 at 03:58:02PM -0500, Eric Sunshine wrote:
> On Mon, Nov 14, 2022 at 11:53 PM Taylor Blau <me@ttaylorr.com> wrote:
> > * ja/worktree-orphan (2022-11-10) 2 commits
> >  - worktree add: add --orphan flag
> >  - worktree add: Include -B in usage docs
> >
> >  'git worktree add' learned how to create a worktree based on an
> >  orphaned branch with `--orphan`.
> >
> >  Waiting for review discussion to settle, but leaning negative.
> >  source: <20221110233137.10414-1-jacobabel@nullpo.dev>
>
> I haven't had a chance yet to look at Jacob's v3, but this series does
> close a gap in worktree usability[*], and v3 addresses a stated
> concern of mine against earlier iterations, so I think a "negative
> lean" may not be warranted.

Thanks for saying so, I dropped this from my notes, so the "leaning
negative" designation will be gone in the next WC.

Thanks,
Taylor

  reply	other threads:[~2022-11-16  2:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15  4:50 What's cooking in git.git (Nov 2022, #03; Mon, 14) Taylor Blau
2022-11-15  4:59 ` Eric Sunshine
2022-11-15  5:01   ` Taylor Blau
2022-11-15  6:28 ` ps/receive-use-only-advertised Patrick Steinhardt
2022-11-15  6:47   ` ps/receive-use-only-advertised Taylor Blau
2022-11-15 17:28     ` ps/receive-use-only-advertised Jeff King
2022-11-16  2:02       ` ps/receive-use-only-advertised Taylor Blau
2022-11-18 23:27       ` ps/receive-use-only-advertised Junio C Hamano
2022-11-15  8:06 ` rp/maintenance-qol with 'make DEVELOPER=1' (was: What's cooking in git.git (Nov 2022, #03; Mon, 14)) Ævar Arnfjörð Bjarmason
2022-11-15 14:04 ` ms/sendemail-validate-headers, was Re: What's cooking in git.git (Nov 2022, #03; Mon, 14) Johannes Schindelin
2022-11-16  1:20   ` Taylor Blau
2022-11-16 11:48     ` Strawbridge, Michael
2022-11-18 13:24       ` Johannes Schindelin
2022-11-15 20:58 ` Eric Sunshine
2022-11-16  2:04   ` Taylor Blau [this message]
2022-11-16  6:07 ` Elijah Newren
2022-11-16 20:16   ` 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=Y3RFMrhgVYLR6nZ4@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=jacobabel@nullpo.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.