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
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Aug 24, 2016, 15:39 UTC
Message-ID
<alpine.DEB.2.20.1608241735520.4924@virtualbox>
In-Reply-To
<xmqqzio3uw31.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Tue, 23 Aug 2016, Junio C Hamano wrote:
Show 13 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > 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.

Right. Which is even more a reason for me to decouple this feature from non-Windows Git.

Show 5 quoted lines
> [...] 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.

This is nothing new. As I said earlier, I have plenty of experience with this. Including the experience of worsimproving a feature that has been battle-tested for years, only to be broken in the process to appease reviewers on the Git mailing list.

I talk about the core.hideDotFiles feature, of course, which in the process of being integrated into core Git lost its ability to respect the setting to be "false".

Git for Windows has a work-around already, of course, it's just ugly, so I am hesitating to "upstream it" yet.

As I said. All of this is old hat. Git for Windows has been, and probably will be for a long time to come, diverging from upstream Git. This is not something I wanted, or worked toward. It's just reality that happened and I have to deal with it and there is nothing to see here, please move on.

Ciao, Dscho

Previous: Johannes SchindelinNext: Junio C Hamano
Message 18 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.