From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
Duy Nguyen <pclouds@gmail.com>,
git-for-windows <git-for-windows@googlegroups.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.9.3
Date: Tue, 23 Aug 2016 22:09:57 -0700 [thread overview]
Message-ID: <xmqqbn0iu50a.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1608231758260.4924@virtualbox> (Johannes Schindelin's message of "Tue, 23 Aug 2016 18:05:32 +0200 (CEST)")
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?
next prev parent reply other threads:[~2016-08-24 5:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 10:14 [ANNOUNCE] Git for Windows 2.9.3 Johannes Schindelin
2016-08-13 15:50 ` Junio C Hamano
2016-08-17 13:54 ` Johannes Schindelin
2016-08-17 15:29 ` Junio C Hamano
2016-08-18 8:37 ` Johannes Schindelin
2016-08-22 14:04 ` [git-for-windows] " Duy Nguyen
2016-08-23 13:54 ` Johannes Schindelin
2016-08-23 14:41 ` Michael J Gruber
2016-08-23 15:37 ` Johannes Schindelin
2016-08-23 16:05 ` Johannes Schindelin
2016-08-23 19:25 ` Junio C Hamano
2016-08-23 21:42 ` Junio C Hamano
2016-08-24 1:04 ` Dakota Hawkins
2016-08-24 15:41 ` Git for Windows documentation, was " Johannes Schindelin
2016-08-24 16:06 ` Dakota Hawkins
2016-08-24 23:28 ` Philip Oakley
2016-08-25 11:42 ` Johannes Schindelin
2016-08-24 15:39 ` Johannes Schindelin
2016-08-24 5:09 ` Junio C Hamano [this message]
2016-08-24 15:48 ` core.autocrlf, was " Johannes Schindelin
2016-08-24 16:45 ` Junio C Hamano
2016-08-25 11:54 ` Johannes Schindelin
2016-08-25 12:43 ` Torsten Bögershausen
2016-08-25 13:50 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbn0iu50a.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).