From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Patrick Steinhardt <ps@pks.im>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 2/3] contrib/buildsystems: drop support for building .vcproj/.vcxproj files
Date: Mon, 5 May 2025 15:46:14 +0200 (CEST) [thread overview]
Message-ID: <ddcbbd1a-dd36-a115-aa77-d5bd3c210cd7@gmx.de> (raw)
In-Reply-To: <aBi8KQWP4YAi6Gph@pks.im>
Hi Patrick,
On Mon, 5 May 2025, Patrick Steinhardt wrote:
> [I] wonder whether we also want to get rid of "contrib/vscode", which is
> similar in spirit. Both Meson and CMake can be used natively with
> VSCode.
I would like to avoid that, as the `contrib/vscode/` files do not even
have anything in the way of building Git. Instead, there is a
configuration that allows Intellisense to find the symbols' declarations
and definitions, and it specifies a little bit the style conventions as
well as common terms that the cSpell checker benefits from.
I use this on almost a daily basis, so I believe that `contrib/vscode/` is
in a _much_ better shape than `contrib/buildsystems/`' Visual Studio
support code ever was. For that reason, I am a lot more in favor of
keeping the `vscode/` stuff.
Ciao,
Johannes
next prev parent reply other threads:[~2025-05-05 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 7:39 [PATCH 0/3] Some CI/buildsystems cleanup Johannes Schindelin via GitGitGadget
2025-05-05 7:39 ` [PATCH 1/3] ci: stop linking the `prove` cache Johannes Schindelin via GitGitGadget
2025-05-05 7:39 ` [PATCH 2/3] contrib/buildsystems: drop support for building .vcproj/.vcxproj files Johannes Schindelin via GitGitGadget
2025-05-05 13:24 ` Patrick Steinhardt
2025-05-05 13:46 ` Johannes Schindelin [this message]
2025-05-05 14:33 ` Patrick Steinhardt
2025-06-02 8:38 ` Johannes Schindelin
2025-06-02 15:04 ` Junio C Hamano
2025-05-05 7:39 ` [PATCH 3/3] config.mak.uname: drop the `vcxproj` target Johannes Schindelin via GitGitGadget
2025-05-05 13:52 ` [PATCH 0/3] Some CI/buildsystems cleanup 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=ddcbbd1a-dd36-a115-aa77-d5bd3c210cd7@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=ps@pks.im \
/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).