Re: [FAQ?] Rationale for git's way to manage the index
- From
Junio C Hamano <junkio@cox.net>
- Date
- May 12, 2007, 00:40 UTC
- Message-ID
- <7vlkfu98nn.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <200705120106.53624.jnareb@gmail.com>
Jakub Narebski <jnareb@gmail.com> writes:
> -'git-add' [-n] [-v] [-f] [--interactive | -i] [-u] [--] <file>... > +'git-add' [-n] [-v] [-f] (-u [[--] <file>...] | [--] <file>...)
I do not think this is correct; does -u take optionally path and when path is ambiguous you can add -- to disambiguate?
Honestly, I would rather not sprinkle synopsis with too many nested parentheses and brackets, which only makes it harder to see without giving a clear "this combines with that but is not compatible with the other" information. Adding comment to the section that begins with "-u::" that says "... commit -a; this option does not take any paths parameters." would be cleaner, and easier to understand.
Of course, I would prefer a patch to allow use of paths with -u even more, but that is what I already said ;-).