From: Jonas Fonseca <fonseca@diku.dk>
To: Ben Clifford <benc@hawaga.org.uk>
Cc: Git List <git@vger.kernel.org>, Petr Baudis <pasky@ucw.cz>
Subject: Re: [PATCH] cg-completion: improve options and command listing
Date: Sun, 18 Dec 2005 15:34:39 +0100 [thread overview]
Message-ID: <20051218143439.GA7064@diku.dk> (raw)
In-Reply-To: <EF827EE8-7B7A-4D19-A08D-8C67D6B74195@hawaga.org.uk>
Ben Clifford <benc@hawaga.org.uk> wrote Sun, Dec 18, 2005:
>
> On 12 Dec 2005, at 04:39, Jonas Fonseca wrote:
>
> >Complete help options and improve filtering for command name
> >completion.
> >
> >Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
> >
>
> Hi. I've applied this patch to the dev branch cg-compl in my
> gitcompletion repo.
>
> I'm interested by what you mean by 'all sorts of garbage' - it seems
> ok on my machine.
~/src/cogito/cogito > __cg_cmdlist | head
cg-add Add files to the GIT repository.
cg-clean Clean unknown files from the working tree.
cg-clone Clone a remote GIT repository.
cg-commit Commit into a GIT repository.
cg-diff Make a diff between two GIT trees.
cg-export Exports a particular revision from a GIT repository.
cg-fetch Fetch changes from a remote branch to the local GIT repository.
cg-help Show help for Cogito commands.
cg-init Initialize a GIT repository.
cg-log Make a log of changes in a GIT branch.
Else I was thinking of maybe adding --list parameter to cg-help to have
it list all known commands.
--
Jonas Fonseca
next prev parent reply other threads:[~2005-12-18 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-11 19:09 [PATCH] cg-completion: improve options and command listing Jonas Fonseca
2005-12-17 23:25 ` Ben Clifford
2005-12-18 14:34 ` Jonas Fonseca [this message]
2005-12-19 1:03 ` Ben Clifford
2005-12-20 2:13 ` Ben Clifford
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=20051218143439.GA7064@diku.dk \
--to=fonseca@diku.dk \
--cc=benc@hawaga.org.uk \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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).