From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Marc Khouzam" <marc.khouzam@gmail.com>,
"Felipe Contreras" <felipe.contreras@gmail.com>,
"Marius Storm-Olsen" <marius@storm-olsen.com>,
"Marius Storm-Olsen" <mstormo@gmail.com>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Peter van der Does" <peter@avirtualhome.com>,
"SZEDER Gábor" <szeder@ira.uka.de>,
"Mark Lodato" <lodatom@gmail.com>
Subject: [PATCH v6 0/2] New zsh wrapper
Date: Sun, 18 Nov 2012 12:08:07 +0100 [thread overview]
Message-ID: <1353236889-15052-1-git-send-email-felipe.contreras@gmail.com> (raw)
Hi,
It looks like there's some resistance with the other patches this series was
depending upon, so lets get rid of them, they are not really needed.
This version should be ready to merge.
The second patch is new, in order for users to get the same features when
sourcing the bash script (they don't need to change anything). They'll get a
warning suggesting to check the new script git-completion.zsh. Eventually, that
support would be dropped from the bash script.
Some people were suggesting something like this, so here it is.
Can we merge the zsh wrapper now?
Felipe Contreras (2):
completion: add new zsh completion
completion: start moving to the new zsh completion
contrib/completion/git-completion.bash | 104 +++++++++++++++++++--------------
contrib/completion/git-completion.zsh | 78 +++++++++++++++++++++++++
2 files changed, 139 insertions(+), 43 deletions(-)
create mode 100644 contrib/completion/git-completion.zsh
--
1.8.0
next reply other threads:[~2012-11-18 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 11:08 Felipe Contreras [this message]
2012-11-18 11:08 ` [PATCH v6 1/2] completion: add new zsh completion Felipe Contreras
2012-11-18 11:08 ` [PATCH v6 2/2] completion: start moving to the " Felipe Contreras
2012-11-19 18:55 ` [PATCH v6 0/2] New zsh wrapper Junio C Hamano
2012-11-19 21:56 ` Felipe Contreras
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=1353236889-15052-1-git-send-email-felipe.contreras@gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=lodatom@gmail.com \
--cc=marc.khouzam@gmail.com \
--cc=marius@storm-olsen.com \
--cc=mstormo@gmail.com \
--cc=peter@avirtualhome.com \
--cc=szeder@ira.uka.de \
/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