From: Jens Lehmann <Jens.Lehmann@web.de>
To: Nicolas Morey-Chaisemartin <devel-git@morey-chaisemartin.com>
Cc: Shawn Pearce <spearce@spearce.org>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH v2] git-completion: Add support for git submodule options
Date: Mon, 11 Apr 2011 19:59:54 +0200 [thread overview]
Message-ID: <4DA3419A.4080809@web.de> (raw)
In-Reply-To: <4DA33EC8.5040704@morey-chaisemartin.com>
Am 11.04.2011 19:47, schrieb Nicolas Morey-Chaisemartin:
> Completion for git submodule only handled subcommands.
> Add support for options of each subcommand
>
> Signed-off-by: Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>
I don't know much about the internals of completion, but I like where
this is heading.
next prev parent reply other threads:[~2011-04-11 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 17:47 [PATCH v2] git-completion: Add support for git submodule options Nicolas Morey-Chaisemartin
2011-04-11 17:59 ` Jens Lehmann [this message]
2011-04-12 9:37 ` SZEDER Gábor
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=4DA3419A.4080809@web.de \
--to=jens.lehmann@web.de \
--cc=devel-git@morey-chaisemartin.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).