From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Philip Oakley <firstname.lastname@example.org>
Cc: Jeff Hostetler <email@example.com>, GitList <firstname.lastname@example.org>
Subject: Re: [PATCH] compat/vcbuild/README: clean/update 'vcpkg' env for Visual Studio updates
Date: Tue, 28 May 2019 20:06:42 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.email@example.com> (raw)
On Tue, 28 May 2019, Philip Oakley wrote:
> On 28/05/2019 14:56, Jeff Hostetler wrote:
> > Did you mean to send this upstream or to Git for Windows?
> > I didn't think that the VS2015/VS2017 vcpkg-aware version of
> > compat/vcbuild/* had made it upstream yet, so this patch might not
> > apply upstream.
> Ah, that would be my mistake.
An understandable one, as I had originally planned on trying to get the
MSVC/Visual Studio patches into git.git after the v2.21.0 release.
However, I deemed the built-in `add -p` a bit more pressing, as it
directly affects my workflow, and the MSVC patches already made it into
Git for Windows (and are continuously tested by our Azure Pipeline).
My current plan is to "upstream" the MSVC patches directly after v2.22.0
prev parent reply other threads:[~2019-05-28 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 12:08 [PATCH] compat/vcbuild/README: clean/update 'vcpkg' env for Visual Studio updates Philip Oakley
2019-05-28 13:56 ` Jeff Hostetler
2019-05-28 14:09 ` Philip Oakley
2019-05-28 14:32 ` Jeff Hostetler
2019-05-28 18:06 ` Johannes Schindelin [this message]
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).