Re: [PATCH v8 2/4] cat-file: teach cat-file a '--literally' option
- From
Charles Bailey <charles@hashpling.org>
- Date
- Apr 21, 2015, 10:16 UTC
- Message-ID
- <20150421101641.GA13202@hashpling.org>
- In-Reply-To
- <553520CF.6070304@gmail.com>
On Mon, Apr 20, 2015 at 09:22:47PM +0530, karthik nayak wrote:
Show 12 quoted lines
> > > On 04/20/2015 02:49 PM, Charles Bailey wrote: > >As far as I could tell - and please correct me if I've misunderstood, > >cat-file's literally is about dealing with unrecognized types whereas > >hash-object's --literally is about both creating objects with bad types > >and invalid objects of "recognized" types. This latter scenario is where > >the option name "literally" makes the most sense. > Yes. What you're saying is correct, but it also makes sense as we're asking > "cat-file" to give us information about the object irrespective of the type of the > object, hence asking it to literally print the information. Also it stays as a compliment > to "hash-object --literally", which is already existing.
OK, I think you've hit the main point which I was trying to make.
To me, "literally" means "without transformation" or "exactly as written/recorded/transmitted" (which -t/-s do anyway) and doesn't really encompass the "irrespective of type" meaning that it has been given here.
In any case, I've made my point so I won't labour it any further. I think that --no-validation or --allow-any-type might be more accurate but if everyone else is happy enough with --literally then I'm happy to live with that too.