From: 'Jacob Abel' <jacobabel@nullpo.dev>
To: rsbecker@nexbridge.com
Cc: "'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>,
"'Eric Sunshine'" <sunshine@sunshineco.com>,
"'Phillip Wood'" <phillip.wood123@gmail.com>,
"'Rubén Justo'" <rjusto@gmail.com>,
"'Taylor Blau'" <me@ttaylorr.com>,
git@vger.kernel.org
Subject: Re: [PATCH v3 0/2] worktree: Support `--orphan` when creating new worktrees
Date: Mon, 12 Dec 2022 00:38:00 +0000 [thread overview]
Message-ID: <20221212003509.t4pucrlxxl5htj62@phi> (raw)
In-Reply-To: <007001d90b50$8ee3c000$acab4000$@nexbridge.com>
On 22/12/08 05:00PM, rsbecker@nexbridge.com wrote:
>
> I am not sure this is entirely related, but there is a gap in worktree
> configuration, specifically includeIf that I was working on, but suspended
> waiting for worktree code to stabilize. Do you have a sense as to whether this
> might run into this topic?
>
> Regards,
> Randall
I may be mistaken as I'm still pretty new with respect to contributing to git
but I don't believe the two should conflict.
next prev parent reply other threads:[~2022-12-12 0:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 21:41 [PATCH v3 0/2] worktree: Support `--orphan` when creating new worktrees Jacob Abel
2022-12-08 22:00 ` rsbecker
2022-12-12 0:38 ` 'Jacob Abel' [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-04 1:02 [PATCH 0/4] " Jacob Abel
2022-11-04 21:34 ` [PATCH v2 0/2] " Jacob Abel
2022-11-10 23:32 ` [PATCH v3 " Jacob Abel
2022-11-16 0:39 ` Eric Sunshine
2022-11-17 10:00 ` Ævar Arnfjörð Bjarmason
2022-11-19 3:47 ` Jacob Abel
2022-11-19 11:48 ` Ævar Arnfjörð Bjarmason
2022-11-22 5:16 ` Eric Sunshine
2022-11-22 23:26 ` Jacob Abel
2022-11-22 23:55 ` Ævar Arnfjörð Bjarmason
2022-11-23 2:47 ` Jacob Abel
2022-11-23 2:43 ` Rubén Justo
2022-11-23 5:37 ` Jacob Abel
2022-11-23 7:35 ` Rubén Justo
2022-11-22 14:45 ` Phillip Wood
2022-11-23 4:21 ` Jacob Abel
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221212003509.t4pucrlxxl5htj62@phi \
--to=jacobabel@nullpo.dev \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=phillip.wood123@gmail.com \
--cc=rjusto@gmail.com \
--cc=rsbecker@nexbridge.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).