git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.9.3

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 23, 2016, 19:25 UTC
Message-ID
<xmqqzio3uw31.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<alpine.DEB.2.20.1608231758260.4924@virtualbox>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 7 quoted lines
> In case it is not crystal-clear, let me clarify one very important point.
> It seems that some people mistake the work I do for something I do on a
> whim. This is not so.
>
> The patch series that triggered this entire unfortunate discussion
> introduced the --smudge option, which I have subsequently renamed to
> --filters and submitted as a patch series to the Git project.

As the "--filters" is meant as a new feature, it will not land on the maintenance track. It is very likely that it won't be in 2.10, so it won't appear in 2.10.x maintenance track, either.

I do not agree with Duy that the "port to Windows" needs a separate distinct name, though. Having said that, aside from the issue of handling of bugreports has been already meantioned, which mostly costs for Git developers, whatever new feature you unleash ahead of upstream to your Windows port has cost to your end-users. Its implementation or its external interface may have to change when you upstream the new feature that has already been in the field, and your end-users would have to adjust their scripts and/or muscle memory.

One way to avoid that risk may be to release the new feature as "experimental-and-subject-to-change", so that interested users on Windows can actually try it out to see if the feature itself (whatever its interface to them is) makes sense, and you can gauge the value of upstreaming it, while cautioning these early adopters that it has not fully been through the usual review process and may have to change while becoming part of the official release. This is no different from various "experimental features" we unleash to the wild, either via 'master' or keeping it in 'next' (we tend to do more of the latter, marking "see if anybody screams").

Previous: Johannes SchindelinNext: Junio C Hamano
Message 11 of 24 in “[ANNOUNCE] Git for Windows 2.9.3”
  1. Johannes SchindelinAug 13, 2016
  2. Junio C HamanoAug 13, 2016
  3. Johannes SchindelinAug 17, 2016
  4. Junio C HamanoAug 17, 2016
  5. Johannes SchindelinAug 18, 2016
  6. Duy NguyenAug 22, 2016
  7. Johannes SchindelinAug 23, 2016
  8. Michael J GruberAug 23, 2016
  9. Johannes SchindelinAug 23, 2016
  10. Johannes SchindelinAug 23, 2016
  11. Junio C HamanoAug 23, 2016
  12. Junio C HamanoAug 23, 2016
  13. Dakota HawkinsAug 24, 2016
  14. Git for Windows documentation, was Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.9.3Johannes Schindelin, Aug 24, 2016
  15. Dakota HawkinsAug 24, 2016
  16. Philip OakleyAug 24, 2016
  17. Johannes SchindelinAug 25, 2016
  18. Johannes SchindelinAug 24, 2016
  19. Junio C HamanoAug 24, 2016
  20. core.autocrlf, was Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.9.3Johannes Schindelin, Aug 24, 2016
  21. Junio C HamanoAug 24, 2016
  22. Johannes SchindelinAug 25, 2016
  23. Torsten BögershausenAug 25, 2016
  24. Johannes SchindelinAug 25, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.