From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: David Kastrup <dak@gnu.org>, Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH 0/3] git-help -i (info): finishing touches
Date: Mon, 10 Dec 2007 02:06:51 -0800 [thread overview]
Message-ID: <7v8x42n9s4.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1197279969-10613-1-git-send-email-gitster@pobox.com> (Junio C. Hamano's message of "Mon, 10 Dec 2007 01:46:06 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> This series attempts to add finishing touches to "git help -i" (info)
> support.
Side note. The patches I sent out are queued for 'next', and I'll push
it out shortly. I am hoping, after this series graduates to 'master',
to be able to tag v1.5.4-rc0 and declare 'master' as feature complete
for now, and see everybody move to bugfix-only mode.
Currently, the man pages are sorted in $(wildcard) order in the main
menu, but I think:
* make git(7) the first node after Top;
* order the commands in the main @menu to follow the command-list.txt
categorization, and show Porcelains and then Plumbings, just like
git(7) does;
would make the organization better, but I did not do that tonight. I'd
leave that as an exercise to interested readers.
I also briefly considered rolling the manual pages into git.info which
is built from the user manual, but I decided against it for now. I
think the current organization of the user manual is good as a
standalone document, and making the manual set as its appendix is
possible but not necessary. I can be persuaded differently, though.
next parent reply other threads:[~2007-12-10 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1197279969-10613-1-git-send-email-gitster@pobox.com>
2007-12-10 10:06 ` Junio C Hamano [this message]
2007-12-11 5:22 ` [PATCH 0/3] git-help -i (info): finishing touches Christian Couder
2007-12-11 5:27 ` Junio C Hamano
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=7v8x42n9s4.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
/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).