[...] > 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.
