All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: GIT Mailing-list <git@vger.kernel.org>,  Taylor Blau <me@ttaylorr.com>
Subject: Re: [PATCH] t/meson.build: remove deleted performance test script
Date: Fri, 18 Apr 2025 10:40:39 -0700	[thread overview]
Message-ID: <xmqqmscdbc6g.fsf@gitster.g> (raw)
In-Reply-To: <67c50fde-d29c-404b-a296-9f0e482acaf3@ramsayjones.plus.com> (Ramsay Jones's message of "Fri, 18 Apr 2025 17:59:18 +0100")

Ramsay Jones <ramsay@ramsayjones.plus.com> writes:

> Commit 8b0b5c7046 (p5312: removed duplicate performance test script,
> 2025-04-17) removed the 't/perf/p5312-pack-bitmaps-revs.sh' script, but
> forgot to remove it from 't/meson.build', resulting in a broken build.
>
> In order to fix the build, remove the script from 't/meson.build'.

Thanks.


> Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
> ---
>
> Hi Taylor, Junio,
>
> If you need to re-roll the 'tb/pack-bitmap-lookup-tables' branch, could
> you please squash this into commit 8b0b5c7046. (the meson build on the
> current 'seen' branch is broken otherwise).

Unless the topic by Tayor gets rebased on top of what contains
ps/meson-build-perf-bench, which is not even in 'next' (hence I
wouldn't recommend doing such a rebase), this needs to be dealt with
as an evil-merge semantic conflict fix-up, which I did this morning
and pushed the result out.

  reply	other threads:[~2025-04-18 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 16:59 [PATCH] t/meson.build: remove deleted performance test script Ramsay Jones
2025-04-18 17:40 ` Junio C Hamano [this message]
2025-04-18 18:52   ` Ramsay Jones
2025-04-18 19:51     ` 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=xmqqmscdbc6g.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    --cc=ramsay@ramsayjones.plus.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.