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: core.autocrlf, was Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.9.3
Date: Wed, 24 Aug 2016 09:45:52 -0700 [thread overview]
Message-ID: <xmqq37luru7z.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1608241743460.4924@virtualbox> (Johannes Schindelin's message of "Wed, 24 Aug 2016 17:48:40 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> 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.
>
> I would advocate against that. It is not like the terms "hash-object" and
> "cat-file" even *look* like they are opposites.
I do not quite understand your objection.
hash-object is "I have data somewhere on the filesystem, and I want
to store it in the object store even though I am not ready to add it
to the index yet (or I may not even add it to the index ever), just
to make it available to Git tools". cat-file is "I have data in the
object store, I want to make it available to my other tools that
understand data stored on the filesystem."
When we taught "--no-filters" to "hash-object" back in 2008, we
should have realized that "cat-file :path >path" would want to be a
way to do "checkout path" (with "--no-filters" option to allow us to
inspect the "canonical version"), but we didn't.
Yes, correcting ancient mistakes is costly. Such is life.
next prev parent reply other threads:[~2016-08-24 16:46 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
2016-08-24 15:48 ` core.autocrlf, was " Johannes Schindelin
2016-08-24 16:45 ` Junio C Hamano [this message]
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=xmqq37luru7z.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).