From: Peter van der Does <peter@avirtualhome.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Peter van der Does <peter@avirtualhome.com>,
git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>
Subject: [PATCH v5 0/2] Make git-completion Bash 4 compatible.
Date: Wed, 1 Dec 2010 19:40:42 -0500 [thread overview]
Message-ID: <1291250444-1832-1-git-send-email-peter@avirtualhome.com> (raw)
Updates since v4
- Patch is based on master again. My mistake.
Peter van der Does (2):
Introduce functions from bash-completion project.
Use the new functions to get the current cword.
contrib/completion/git-completion.bash | 446 ++++++++++++++++++++++++++------
1 files changed, 363 insertions(+), 83 deletions(-)
--
1.7.3.2
next reply other threads:[~2010-12-02 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 0:40 Peter van der Does [this message]
2010-12-02 0:40 ` [PATCH v5 1/2] Introduce functions from bash-completion project Peter van der Does
2010-12-02 0:40 ` [PATCH v5 2/2] Use the new functions to get the current cword Peter van der Does
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=1291250444-1832-1-git-send-email-peter@avirtualhome.com \
--to=peter@avirtualhome.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--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).