From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git@vger.kernel.org,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Victoria Dye" <vdye@github.com>,
"Eric Sunshine" <ericsunshine@gmail.com>
Subject: Re: [PATCH] cmake: don't invoke msgfmt with --statistics
Date: Tue, 20 Dec 2022 09:43:02 +0900 [thread overview]
Message-ID: <xmqqcz8e29d5.fsf@gitster.g> (raw)
In-Reply-To: <45d8d9fc-ca68-5902-0aa7-70034f8383ff@dunelm.org.uk> (Phillip Wood's message of "Mon, 19 Dec 2022 15:00:06 +0000")
Phillip Wood <phillip.wood123@gmail.com> writes:
> On 19/12/2022 10:26, Ævar Arnfjörð Bjarmason wrote:
>> In [1] I made the same change to our Makefile, let's follow-up and do
>> the same here.
>> For "cmake" this is particularly nice with "-G Ninja", as before
>> we'd
>> emit ~40 lines of overflowed progress bar output, but now it's only
>> the one line of "ninja"'s progress bar.
>
> I don't really have a strong opinion either way on this but if it
> matches what we do in the Makefile than it sounds sensible.
As a one-shot change, it might be sensible to claim consistency by
saying "we do the same thing in two places", but I'd worry more
about the root cause of such inconsistency in the first place, i.e.
can we have some trick to ensure that two build systems will not
reimplement the same thing slightly differently?
It also is worth examining if having "the same change" is a good
idea in the first place. The justification given "In [1]" was that
a build driven by our Makefile were concise and non-verbose overall,
but with --stat that concise output pattern was broken.
I do not know (and I do not have particular interest in knowing) how
a build driven by cmake looks like, but does it also aim the same
concise output where output --stat does not fit well, or do folks
who daily build with cmake find the output with --stat sit well in
the output from other things given there? If the latter, making
"the same change" as the Makefile side may not make much sense.
next prev parent reply other threads:[~2022-12-20 0:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 10:26 [PATCH] cmake: don't invoke msgfmt with --statistics Ævar Arnfjörð Bjarmason
2022-12-19 15:00 ` Phillip Wood
2022-12-20 0:43 ` Junio C Hamano [this message]
2022-12-27 13:51 ` Ævar Arnfjörð Bjarmason
2022-12-27 22:33 ` Junio C Hamano
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=xmqqcz8e29d5.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=ericsunshine@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@gmail.com \
--cc=vdye@github.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).