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 24, 2016, 05:09 UTC
Message-ID
<xmqqbn0iu50a.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<alpine.DEB.2.20.1608231758260.4924@virtualbox>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> The feature in question is also highly unlikely to be used as much by
> non-Windows users as by Windows users due to the unfortunate choice of the
> default setting for core.autocrlf.

My vague recollection from some years ago was that even among those who were active in msysGit development there were people who advocated for straight-thru and others who wanted core.autocrlf as the default, but I do not know the current state of the affairs.

In any case, in the ideal future, I would imagine that we would want to have "cat-file blob" to enable "--filters" by default; that would make cat-file and hash-objects a pair of symmetric operations.

That certainly will not happen within 2.x timeframe, and the new "cat-file --filter" feature can appear in 2.11 at the earliest, but I think by that time (or with a few more cycles) we may have a handful other improvements that are backward incompatible lined up to urge us to think about bumping the version number to 3.0. I recall writing "Will keep in next to see if anybody screams" a few times already, and they are all good excuses to invite a version bump.

To prepare for that future, we would probably want to start updating in-tree scripts (including the tests) so that they call "cat-file --no-filter blob" whereever they currently say "cat-file blob" in or soon after 2.11. Of course, if some of them currently pipe "cat-file blob" output to munge it to produce what --filters would have done (I didn't check), we would want to rewrite them to use the new feature "cat-file --filter blob" when we do so. In short, there won't be any "cat-file blob" call that does not have either --filters or --no-filters, except the ones we write specifically to check the updated default behaviour when that happens.

Would that sound like a good longer-term plan?
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 19 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.