From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Emily Shaffer" <emilyshaffer@google.com>,
git@vger.kernel.org, "Robert Foss" <robert.foss@linaro.org>,
"Drew DeVault" <sir@cmpwn.com>,
"Rafael Aquini" <aquini@redhat.com>,
"Marcelo Arenas Belón" <carenas@gmail.com>
Subject: Re: [PATCH v3] git-send-email: Respect core.hooksPath setting
Date: Tue, 23 Mar 2021 18:17:28 -0700 [thread overview]
Message-ID: <xmqq7dlx1hav.fsf@gitster.g> (raw)
In-Reply-To: <87zgytpehg.fsf@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Wed, 24 Mar 2021 01:44:27 +0100")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> While I'd like to see it land I'm skeptical of parts of that approach[1]
> and expect we'll have more re-rolls of it, and in any case the conflict
> in send-email[2] will be trivial to resolve.
> So I think it makes sense
> to queue up this narrow fix and not have this wait on the larger topic.
Well, that is what I am doing for now, queue up this narrow change,
while resolving the conflict to use Emily's topic. Which means that
the new code this topic adds is never exercised while the other topic
is still cooking in tree.
> 1. https://lore.kernel.org/git/87mtv8fww3.fsf@evledraar.gmail.com/
> 2. https://lore.kernel.org/git/20210311021037.3001235-36-emilyshaffer@google.com/
prev parent reply other threads:[~2021-03-24 1:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 16:27 [PATCH v2] git-send-email: Respect core.hooksPath setting Robert Foss
2021-03-23 17:33 ` [PATCH v3] " Ævar Arnfjörð Bjarmason
2021-03-23 22:40 ` Junio C Hamano
2021-03-24 0:44 ` Ævar Arnfjörð Bjarmason
2021-03-24 1:17 ` 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
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=xmqq7dlx1hav.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=aquini@redhat.com \
--cc=avarab@gmail.com \
--cc=carenas@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=robert.foss@linaro.org \
--cc=sir@cmpwn.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).