From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/4] make linux32 ci job work with recent actions
Date: Thu, 12 Sep 2024 12:41:07 -0700 [thread overview]
Message-ID: <xmqqfrq44q3w.fsf@gitster.g> (raw)
In-Reply-To: <20240912094238.GA589050@coredump.intra.peff.net> (Jeff King's message of "Thu, 12 Sep 2024 05:42:38 -0400")
Jeff King <peff@peff.net> writes:
> OK, here's what I came up with. I built it on top of what you have
> queued in jc/ci-upload-artifact-and-linux32, but it could be applied
> separately (and it should merge OK).
Will queue.
Let's target to merge this down to 'maint'; sooner the better.
Thanks.
next prev parent reply other threads:[~2024-09-12 19:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 23:00 [PATCH] ci: remove 'Upload failed tests' directories' step from linux32 jobs Junio C Hamano
2024-09-11 22:32 ` Junio C Hamano
2024-09-12 7:56 ` Jeff King
2024-09-12 8:00 ` Jeff King
2024-09-12 9:42 ` [PATCH 0/4] make linux32 ci job work with recent actions Jeff King
2024-09-12 9:43 ` [PATCH 1/4] ci: drop run-docker scripts Jeff King
2024-09-12 10:40 ` Patrick Steinhardt
2024-09-12 9:45 ` [PATCH 2/4] ci: unify ubuntu and ubuntu32 dependencies Jeff King
2024-09-12 10:41 ` Patrick Steinhardt
2024-09-12 9:47 ` [PATCH 3/4] ci: use more recent linux32 image Jeff King
2024-09-12 10:41 ` Patrick Steinhardt
2024-09-12 11:22 ` Jeff King
2024-09-12 11:53 ` Patrick Steinhardt
2024-09-12 12:47 ` Patrick Steinhardt
2024-09-13 4:55 ` Jeff King
2024-09-13 5:39 ` Patrick Steinhardt
2024-09-12 9:48 ` [PATCH 4/4] ci: use regular action versions for linux32 job Jeff King
2024-09-12 19:41 ` Junio C Hamano [this message]
2024-09-13 5:52 ` [PATCH 5/4] ci: add Ubuntu 16.04 job to GitLab CI Patrick Steinhardt
2024-09-13 6:21 ` Jeff King
2024-09-13 6:39 ` Patrick Steinhardt
2024-09-13 6:43 ` Jeff King
2024-09-13 6:47 ` Patrick Steinhardt
2024-09-13 16:17 ` 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=xmqqfrq44q3w.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.