zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: "{ } always { }" construct and return in called functions
Date: Sat, 23 May 2015 10:49:06 +0000	[thread overview]
Message-ID: <20150523104906.GG1889@tarsus.local2> (raw)
In-Reply-To: <20150522233113.76b13026@ntlworld.com>

Peter Stephenson wrote on Fri, May 22, 2015 at 23:31:13 +0100:
> This is the last thing I have to look at; is anyone else expecting
> something to happen?

[ I assume you're asking if there are release blockers. ]

I *think* the compdescribe stuff is fine.  All of the issues discussed
in that thread are either not new or not happening in master.  My main
concern is that 35127#1 might have introduced a bug that hasn't been
noticed yet.  I'm more concerned about that patch than usual since it is
my first patch to comp*.c and I'm not at home in that part of the code, yet.

Cheers,

Daniel


  parent reply	other threads:[~2015-05-23 10:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHfspHmUOgLjnEMtLBBoeU31Z2GKu8uD5MYE4jsogMKbf+ag9g@mail.gmail.com>
     [not found] ` <20150513155915.71f3daaa@pwslap01u.europe.root.pri>
2015-05-18 11:38   ` Mikael Magnusson
2015-05-18 12:14     ` Peter Stephenson
2015-05-18 12:24       ` Mikael Magnusson
2015-05-18 12:47         ` Peter Stephenson
2015-05-19  5:04           ` Bart Schaefer
2015-05-19  6:22             ` Mikael Magnusson
2015-05-19  6:31               ` Mikael Magnusson
2015-05-20 17:31               ` Bart Schaefer
2015-05-22 22:31     ` Peter Stephenson
2015-05-22 22:46       ` Bart Schaefer
2015-05-23 10:49       ` Daniel Shahaf [this message]
2015-05-23 15:13       ` Mikael Magnusson
2015-05-27  2:20         ` Dave Yost
2015-05-30  0:31           ` Bang-four (Re: "{ } always { }" construct and return in called functions) Bart Schaefer
2015-05-23 22:32       ` Release blocker (was: " Daniel Hahler
2015-05-24 12:54         ` Peter Stephenson
2015-05-26  9:03           ` Peter Stephenson

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=20150523104906.GG1889@tarsus.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@zsh.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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).