threads / discuss / 31931

git commit-tree man page

Subject: git commit-tree man page

## tl;dr

2 messages between Oct 24, 2012 and Oct 24, 2012.

replies: 1people: 2as markdown or json

Angelo Borsotti· Oct 24, 2012, 12:45 UTC · lore
Hello,
the man page of git commit-tree SYNOPSIS is:
    git commit-tree <tree> [(-p <parent>)...] < changelog
    git commit-tree [(-p <parent>)...] [(-m <message>)...] [(-F
<file>)...] <tree>

The second form is incorrect: the <tree> must be specified before the options. E.g.

$ git commit-tree -m B 88f7dbd47 fatal: Not a valid object name -m

$ git commit-tree 88f7dbd47 -m B 2f7619ed932787a128a84c4809d7b72ef38257a5

-Angelo Borsotti
Andreas Schwab· Oct 24, 2012, 13:59 UTC · re: Angelo Borsotti · lore

Re: git commit-tree man page

Angelo Borsotti <angelo.borsotti@gmail.com> writes:
Show 13 quoted lines
> Hello,
>
> the man page of git commit-tree SYNOPSIS is:
>
>     git commit-tree <tree> [(-p <parent>)...] < changelog
>     git commit-tree [(-p <parent>)...] [(-m <message>)...] [(-F
> <file>)...] <tree>
>
> The second form is incorrect: the <tree> must be specified before the options.
> E.g.
>
> $ git commit-tree -m B 88f7dbd47
> fatal: Not a valid object name -m
This has been fixed in 1.7.11.4:
 * "git commit-tree" learned a more natural "-p <parent> <tree>" order
   of arguments long time ago, but recently forgot it by mistake.
Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

← back to recent threads