From: Catalin Marinas <catalin.marinas@gmail.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: git@vger.kernel.org
Subject: Re: StGit command completions - and Git ones?
Date: Tue, 4 Oct 2005 08:23:11 +0100 [thread overview]
Message-ID: <b0943d9e0510040023h287b9d44w@mail.gmail.com> (raw)
In-Reply-To: <200510021303.44960.blaisorblade@yahoo.it>
On 02/10/05, Blaisorblade <blaisorblade@yahoo.it> wrote:
> I noticed in your TODO you talk about adding command line completions. I've
> been doing it for my needs, and the thing is still very incomplete, even if
> it's not a "XXX hack hack hack", and I wanted to send this first draft.
Thanks, I will have a look at it.
FYI, the tla-contrib package has a script which automatically
generates the bash completion script from the help messages (well,
only for tla, but can be adapted).
--
Catalin
next prev parent reply other threads:[~2005-10-04 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 11:03 StGit command completions - and Git ones? Blaisorblade
2005-10-02 17:37 ` Horst von Brand
2005-10-03 17:57 ` Blaisorblade
2005-10-04 7:23 ` Catalin Marinas [this message]
2005-10-04 9:57 ` Blaisorblade
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=b0943d9e0510040023h287b9d44w@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=blaisorblade@yahoo.it \
--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).