From: Junio C Hamano <gitster@pobox.com>
To: "Harshil-Jani via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Harshil Jani <harshiljani2002@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Johannes Sixt <j6t@kdbg.org>,
Jeff Hostetler <jeffhost@microsoft.com>
Subject: Re: [PATCH 2/2] mingw: remove msysGit/MSYS1 support
Date: Sun, 18 Dec 2022 12:58:09 +0900 [thread overview]
Message-ID: <xmqq4jttxt0u.fsf@gitster.g> (raw)
In-Reply-To: <xmqqsfhdxxyj.fsf@gitster.g> (Junio C. Hamano's message of "Sun, 18 Dec 2022 11:11:32 +0900")
Junio C Hamano <gitster@pobox.com> writes:
> "Harshil-Jani via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
>> From: Harshil-Jani <harshiljani2002@gmail.com>
>>
>> The msysGit (i.e. Git for Windows 1.x' SDK) is no longer used and the
>> last known user for MSys1 + MinGW has switched to MSys2.
>
> It is curious that we can speak with such a certainty of the lack of
> users of such a popular project. References?
I see J6t mentioning about such a switch,
https://lore.kernel.org/git/c9aec5b6-0a78-a580-3658-5189bd2075a6@kdbg.org/
but I do not know if it is sensible to claim that this was the last
known user switching away. Perhaps
Last time the code around here was modified, which eventually
led to 49d279f8 (windows: include the Python bits when building
Git for Windows, 2022-07-29), the change was carefully written
to keep things unchanged for Msys1, as at least one user
(Johannes Sixt) who did crucial work to support Git on Windows
and we did not want to break Msys1 (yet). In the discussion J6t
confirmed that he no longer is on Msys1 (cf. [*1*]).
to replace the paragraph, with this at the end
[References]
*1* https://lore.kernel.org/git/c9aec5b6-0a78-a580-3658-5189bd2075a6@kdbg.org/)
explain the change (be sure to explain ../THIS_IS_MSYSGIT bit, too,
not just the $(uname_R) bit), and then throw in something like
There may be users other than J6t who needs a working Msys1, but
we can revert this patch if it becomes necessary (i.e. when they
complain).
somewhere?
Thanks.
next prev parent reply other threads:[~2022-12-18 4:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 21:03 [PATCH 0/2] Remove MSys Support Harshil Jani via GitGitGadget
2022-12-05 21:03 ` [PATCH 1/2] mingw: remove duplicate `USE_NED_ALLOCATOR` directive Harshil-Jani via GitGitGadget
2022-12-18 1:54 ` Junio C Hamano
2022-12-05 21:03 ` [PATCH 2/2] mingw: remove msysGit/MSYS1 support Harshil-Jani via GitGitGadget
2022-12-18 2:11 ` Junio C Hamano
2022-12-18 3:58 ` Junio C Hamano [this message]
2023-01-09 7:48 ` Johannes Schindelin
2023-01-09 8:52 ` Junio C Hamano
2022-12-18 2:15 ` [PATCH 0/2] Remove MSys Support Junio C Hamano
2023-01-09 7:36 ` Johannes Schindelin
2023-01-09 8:49 ` Junio C Hamano
2023-02-02 3:51 ` [PATCH v2 " Harshil Jani via GitGitGadget
2023-02-02 3:51 ` [PATCH v2 1/2] mingw: remove duplicate `USE_NED_ALLOCATOR` directive Harshil-Jani via GitGitGadget
2023-02-02 3:51 ` [PATCH v2 2/2] mingw: remove msysGit/MSYS1 support Harshil-Jani via GitGitGadget
2023-02-02 13:59 ` [PATCH v2 0/2] Remove MSys Support Johannes Schindelin
2023-02-02 16:06 ` 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=xmqq4jttxt0u.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=harshiljani2002@gmail.com \
--cc=j6t@kdbg.org \
--cc=jeffhost@microsoft.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).