From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Junio C Hamano <gitster@pobox.com>, Mark Lodato <lodatom@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2010, #07; Wed, 29)
Date: Tue, 12 Oct 2010 23:26:58 +0200 [thread overview]
Message-ID: <20101012212658.GF4536@neumann> (raw)
In-Reply-To: <20101010212646.GA6092@neumann>
Hi,
On Sun, Oct 10, 2010 at 11:26:46PM +0200, SZEDER Gábor wrote:
> On Wed, Sep 29, 2010 at 05:16:10PM -0700, Junio C Hamano wrote:
> > * ml/completion-zsh (2010-09-06) 1 commit
> > (merged to 'next' on 2010-09-22 at d62d10e)
> > + completion: make compatible with zsh
> >
> > Comments from bash users regarding regressions?
>
> No regressions so far here, but I don't use the "divergence from svn
> upstream" feature (although the two changes in that codepath seem to
> be fairly trivial).
There is one regression, though.
We made changes in the past to get the completion script working when
'set -u' is enabled, see commits 25a31f8 (bash-completion: Support
running when set -u is enabled, 2009-01-15) and 6c44b64
(bash-completion: Fix __git_ps1 to work with "set -u", 2010-06-17).
This patch causes an unbound variable error with 'set -u' when it
checks $ZSH_VERSION, which is, of course, undefined in bash.
Following up on 25a31f8, using ${ZSH_VERSION-} avoids such errors
under bash and 'set -u', and I think it should work with zsh, too.
Best,
Gábor
prev parent reply other threads:[~2010-10-12 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 0:16 What's cooking in git.git (Sep 2010, #07; Wed, 29) Junio C Hamano
2010-09-30 3:22 ` Elijah Newren
2010-10-02 8:12 ` Pascal Obry
2010-10-03 4:36 ` Joshua Jensen
2010-10-03 13:30 ` Elijah Newren
2010-10-03 23:34 ` Junio C Hamano
2010-10-10 21:26 ` SZEDER Gábor
2010-10-12 21:26 ` SZEDER Gábor [this message]
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=20101012212658.GF4536@neumann \
--to=szeder@ira.uka.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=lodatom@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).