From: Konstantin Khomoutov <kostix@bswap.ru>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Hello question on Git for Windows 2.43.0 - GUID and/or SWID tag for this title
Date: Fri, 16 Feb 2024 15:56:16 +0300 [thread overview]
Message-ID: <20240216125616.l3iktxfx24vy4jax@carbon> (raw)
In-Reply-To: <LV8PR13MB65609D60ACB8A6EADFBFE3459C4D2@LV8PR13MB6560.namprd13.prod.outlook.com> <20240216110041.dqz2n5dz43mqtq25@carbon>
[...]
> Therefore, please let me know what your role is with Git for Windows so I
> can send this feedback accordingly and continue working on with our software
> inventory vendor on the issue.
[...]
> So, I would recommend to ask on GfW's Github Discussions [2] or on the
> GfW's dedicated mailing list [3].
[...]
> 2. https://github.com/git-for-windows/git/discussions
> 3. https://groups.google.com/g/git-for-windows/
To make things maybe a bit more clear: this very list our discussion is taking
place is dedicated to the development of the "core" Git, and Git-for-Windows
has started years ago as what one would call a continuous friendly fork of
Git. May changes implemented in GfW get upstreamed into the "core" Git,
but GfW still maintains a set of patches atop of Git, as well as a hefty
amount of infrastructure code (because in order to properly function under
Windows, Git requires lots of supporting software which presence is taken for
granted on Unix-like systems but does not normally exist on Windows).
Maintaining a Windows installer binary is also a task.
In other words, GfW has quite specific requirements to still be a separate,
though very close, project, and because of this is has its own separate
supporting infrastructure: a project and issue tracker on Github and its own
communication venues. These venues are what I and someone other earlier in
this discussion have pointed you at.
next prev parent reply other threads:[~2024-02-16 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 18:57 Hello question on Git for Windows 2.43.0 - GUID and/or SWID tag for this title Christian Castro
2024-02-02 19:16 ` Kristoffer Haugsbakk
2024-02-10 7:40 ` Matthias Aßhauer
2024-02-15 21:40 ` Christian Castro
2024-02-16 11:00 ` Konstantin Khomoutov
2024-02-16 12:56 ` Konstantin Khomoutov [this message]
2024-02-18 22:06 ` Johannes Schindelin
2024-02-22 13:35 ` Kristoffer Haugsbakk
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=20240216125616.l3iktxfx24vy4jax@carbon \
--to=kostix@bswap.ru \
--cc=git@vger.kernel.org \
/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).