Message ID | pull.1533.v3.git.git.1688004473941.gitgitgadget@gmail.com (mailing list archive) |
---|---|
State | Accepted |
Commit | d4f28279ada8c8dce6cb13a0c4a13b8d06000af8 |
Headers | show |
Series | [v3] docs: add git hash-object -t option's possible values | expand |
"John Cai via GitGitGadget" <gitgitgadget@gmail.com> writes: > From: John Cai <johncai86@gmail.com> > > The summary under the NAME section for git hash-object can mislead > readers to conclude that the command can only be used to create blobs, > whereas the description makes it clear that it can be used to create > objects, not just blobs. Let's clarify the one-line summary. > > Further, the description for the option -t does not list out other types > that can be used when creating objects. Let's make this explicit by > listing out the different object types. > > Signed-off-by: John Cai <johncai86@gmail.com> > --- Looks good. Queued. Let's merge it down to 'next' and below. Thanks.
diff --git a/Documentation/git-hash-object.txt b/Documentation/git-hash-object.txt index 472b5bb995b..8577f7a7d40 100644 --- a/Documentation/git-hash-object.txt +++ b/Documentation/git-hash-object.txt @@ -3,7 +3,7 @@ git-hash-object(1) NAME ---- -git-hash-object - Compute object ID and optionally creates a blob from a file +git-hash-object - Compute object ID and optionally create an object from a file SYNOPSIS @@ -25,7 +25,8 @@ OPTIONS ------- -t <type>:: - Specify the type (default: "blob"). + Specify the type of object to be created (default: "blob"). Possible + values are `commit`, `tree`, `blob`, and `tag`. -w:: Actually write the object into the object database.