From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 5/8] bash: Classify more commends out of completion.
Date: Sun, 4 Feb 2007 03:16:55 -0500 [thread overview]
Message-ID: <20070204081655.GF16766@spearce.org> (raw)
In-Reply-To: <7vmz3uxryj.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> At some point we might want to generate this part from the table
> defined in Documentation/cmd-list.perl (the latter might need to
> be extended for that, but I think matching "helper", "plumbing"
> and perhaps "foreign" would cover most of them).
Actually I'm thinking of going in the other direction. The set of
commands which we expect people to use in an interactive setting
on the command line is smaller than the set of commands we actually
ship.
But yea, maybe we can build it from the existing sources...
--
Shawn.
next prev parent reply other threads:[~2007-02-04 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 7:38 [PATCH 5/8] bash: Classify more commends out of completion Shawn O. Pearce
2007-02-04 8:11 ` Junio C Hamano
2007-02-04 8:16 ` Shawn O. Pearce [this message]
2007-02-04 10:33 ` Jakub Narebski
2007-02-05 2:37 ` Shawn O. Pearce
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=20070204081655.GF16766@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).