From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Improve error message: not a valid branch name
Date: Sun, 26 Aug 2007 18:25:00 -0400 [thread overview]
Message-ID: <20070826222500.GA9116@fieldses.org> (raw)
In-Reply-To: <ejhqeynj.fsf@cante.net>
On Mon, Aug 27, 2007 at 01:09:20AM +0300, Jari Aalto wrote:
> 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.
prev parent reply other threads:[~2007-08-26 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 15:28 [PATCH] Improve error message: not a valid branch name Jari Aalto
2007-08-26 21:26 ` Junio C Hamano
2007-08-26 22:09 ` Jari Aalto
2007-08-26 22:25 ` J. Bruce Fields [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070826222500.GA9116@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).