From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Jeff Hostetler <jeffhostetler@github.com>
Subject: [PATCH 0/2] add missing LIBCURL prereq to a few tests
Date: Wed, 11 Sep 2024 12:30:58 +0200 [thread overview]
Message-ID: <cover.1726049108.git.martin.agren@gmail.com> (raw)
Hi,
I recently had reason to build Git without libcurl. That surfaced two
test scripts that use `git http-fetch` or similar without giving the
LIBCURL prerequisite.
Martin
Martin Ågren (2):
t1517: add missing LIBCURL prereq
t0211: add missing LIBCURL prereq
t/t0211-trace2-perf.sh | 6 ++++--
t/t1517-outside-repo.sh | 2 +-
2 files changed, 5 insertions(+), 3 deletions(-)
--
2.46.0.733.g1eb83ef1a1
next reply other threads:[~2024-09-11 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 10:30 Martin Ågren [this message]
2024-09-11 10:30 ` [PATCH 1/2] t1517: add missing LIBCURL prereq Martin Ågren
2024-09-11 10:31 ` [PATCH 2/2] t0211: " Martin Ågren
2024-09-11 15:53 ` [PATCH 0/2] add missing LIBCURL prereq to a few tests 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=cover.1726049108.git.martin.agren@gmail.com \
--to=martin.agren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhostetler@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).