git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH 0/2] Update the win+VS build definition
Date: Tue, 20 Aug 2024 08:22:49 -0700	[thread overview]
Message-ID: <xmqqv7zvb4mu.fsf@gitster.g> (raw)
In-Reply-To: <pull.1775.git.1724164270.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Tue, 20 Aug 2024 14:31:08 +0000")

"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:

> These two patches have been in Git for Windows' fork for quite a while.
>
> While the win+VS builds are not run in Git's CI builds, it is still a good
> idea to upstream these changes.
>
> Johannes Schindelin (2):
>   ci: bump microsoft/setup-msbuild from v1 to v2
>   ci(win+VS): download the vcpkg artifacts using a dedicated GitHub
>     Action
>
>  .github/workflows/main.yml | 14 +++++---------
>  1 file changed, 5 insertions(+), 9 deletions(-)

Thanks.  

Do you mind if I applied these directly to 'maint' and merged the
result upwards?

  parent reply	other threads:[~2024-08-20 15:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20 14:31 [PATCH 0/2] Update the win+VS build definition Johannes Schindelin via GitGitGadget
2024-08-20 14:31 ` [PATCH 1/2] ci: bump microsoft/setup-msbuild from v1 to v2 Johannes Schindelin via GitGitGadget
2024-08-20 14:31 ` [PATCH 2/2] ci(win+VS): download the vcpkg artifacts using a dedicated GitHub Action Johannes Schindelin via GitGitGadget
2024-08-20 15:22 ` Junio C Hamano [this message]
2024-08-20 20:15   ` [PATCH 0/2] Update the win+VS build definition Johannes Schindelin
2024-08-20 20:38     ` 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=xmqqv7zvb4mu.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    /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).