Re: [PATCH] Improve error message: not a valid branch name
- From
- J. Bruce Fields <bfields@fieldses.org>
- Date
- Aug 26, 2007, 22:25 UTC
- Message-ID
- <20070826222500.GA9116@fieldses.org>
- In-Reply-To
- <ejhqeynj.fsf@cante.net>
On Mon, Aug 27, 2007 at 01:09:20AM +0300, Jari Aalto wrote:
Show 19 quoted lines
> Junio C Hamano <gitster@pobox.com> writes: > > Two possible improvements that are mutually incompatible would > > be: > > > > - refactor that part of the manual to be included in the pages > > for any and all commands that can take refname from the user; > > this is inpractical as almost all command would be affected. > > > > - move that to more central place, say git(7), and everybody > > refer to that page; > > > > I'd personally prefer the latter, as "naming things" is such a > > central thing for the use of the system (this applies to the > > description of "SHA-1 expression" that we curently have in > > git-rev-parse(1) as well) and it is better for users to have > > understanding of such fundamental syntaxes and concepts before > > even using any individual commands. > > Wholeheartedly concur.
Sounds good to me too, but...
> Should I re-submit the patch to refer to git(7) instead?
... git(7) is pretty long, so finding the referred-to information in that man page might take a while. Would it be possible to put this in a (section 7?) man page of its own?
--b.