Re: [PATCH] docs: add git-hash-object -t option's possible values

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 22, 2023, 23:04 UTC
Message-ID: <xmqqv8ffcd4w.fsf@gitster.g>
In-Reply-To: <ZJOc3Kd0vEEO6bUr@tapette.crustytoothpaste.net>

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

Show 14 quoted lines

> On 2023-06-22 at 00:46:34, John Cai via GitGitGadget wrote:
>> From: John Cai <johncai86@gmail.com>
>> 
>> For newer users of Git, the possible values of -t in git-hash-object may
>> not be apparent. In fact the current verbiage under NAME could
>> lead one to conclude that git-hash-object(1) can only be used to create
>> blobs.
>> 
>> Update the verbiage to make it clear the command can be used to write
>> objects, not just blobs. Also add the possible values for -t.
>
> Sure, I think this is a good change.  I'm of the opinion we should tell
> people explicitly what the valid values are whenever there are a
> reasonable number.

Strictly speaking, the valid values become unbounded under --literally, but it is just for those who build and experiment with Git, not for end-users or toolsmiths, so I am OK with listing the four object types here.

Thanks.