git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Phillip Wood <phillip.wood123@gmail.com>,
	Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: cmake topics & js/ci-disable-cmake-by-default
Date: Wed, 28 Dec 2022 08:06:08 +0900	[thread overview]
Message-ID: <xmqq4jtgsazj.fsf@gitster.g> (raw)
In-Reply-To: <221227.86pmc4vrk3.gmgdl@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Tue, 27 Dec 2022 14:59:20 +0100")

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

> On Tue, Dec 27 2022, Junio C Hamano wrote:
>
>> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>>
>>> I split up the previously merged to "next" ab/cmake-nix-and-ci and
>>> submitted the uncontroversial parts of it as:
>>
>> Not gathering any interest by folks who will be affected is
>> different from being uncontroversial, though.  It may not have seen
>> any controversy so far, but once it reappears in my tree and
>> sufficiently advances to cause trouble to other people, it would.
>>
>> In other words, I am saving time and energy of people by waiting for
>> positive support on these changes.
>
> These changes had made it to "next" already on the basis of the feedback
> the topic already got.

After the topic turned out to be unwanted, I am not sure how much
weight we want to give to the supportive opinions that initially
pushed it to 'next'.

  reply	other threads:[~2022-12-27 23:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26  3:38 What's cooking in git.git (Dec 2022, #07; Mon, 26) Junio C Hamano
2022-12-26 10:52 ` cmake topics & js/ci-disable-cmake-by-default (was: What's cooking in git.git (Dec 2022, #07; Mon, 26)) Ævar Arnfjörð Bjarmason
2022-12-27  4:26   ` cmake topics & js/ci-disable-cmake-by-default Junio C Hamano
2022-12-27 13:59     ` Ævar Arnfjörð Bjarmason
2022-12-27 23:06       ` Junio C Hamano [this message]
2022-12-28  8:36 ` built-in-submodule & in-flight dependencies (was: What's cooking in git.git (Dec 2022, #07; Mon, 26)) Ævar Arnfjörð Bjarmason

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=xmqq4jtgsazj.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --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).