zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Users <zsh-users@zsh.org>
Cc: Danek Duvall <duvall@comfychair.org>
Subject: Re: zsh 5.0.8.-test-3
Date: Wed, 26 Aug 2015 09:48:49 +0100	[thread overview]
Message-ID: <20150826094849.4704e3f7@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <CAHYJk3R82p1XE+cS56uqSf3QfcB_NO8YF4rE74vkRTq-H-7wAg@mail.gmail.com>

On Wed, 26 Aug 2015 04:19:45 +0200
Mikael Magnusson <mikachu@gmail.com> wrote:
> > FWIW, we do have our man pages online:
> >
> >     http://docs.oracle.com/cd/E36784_01/html/E36874/strftime-3c.html
> >
> > which documents # and E and O, as well as ^ and _.  So I don't know why it
> > didn't work, unless the underlying implementation is broken, which is
> > entirely possible (and likely enough that I'd say you should just keep the
> > test as it is and I'll go make sure the appropriate bug is filed and just
> > live with the test failure for now).
> 
> I'll let Peter decide which of those to do then.

It's minor enough that I'm not *that* bothered.

I have a vague prejudice that releasing something with a test failing,
even if it's a "real" failure, is going to cause more trouble than it's
worth for something that's not a core part of the shell and which is new
anyway.  Suppose we apply the test patch now and back it off immediately
after the release?  The released code is still capable of showing the
problem, so this don't make debugging harder.

pws

-- 
Peter Stephenson | Principal Engineer Samsung Cambridge Solution Centre
Email: p.stephenson@samsung.com | Phone: +44 1223 434724 |
www.samsung.com


  reply	other threads:[~2015-08-26  8:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 18:48 Peter Stephenson
2015-08-25 21:57 ` Baptiste Daroussin
2015-08-25 22:22 ` Danek Duvall
2015-08-25 23:09   ` Mikael Magnusson
2015-08-26  1:27     ` Danek Duvall
2015-08-26  2:19       ` Mikael Magnusson
2015-08-26  8:48         ` Peter Stephenson [this message]
2015-08-26  9:30           ` Mikael Magnusson
2015-08-28  8:45             ` Peter Stephenson
2015-08-25 22:36 Michael Beasley

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=20150826094849.4704e3f7@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.com \
    --cc=duvall@comfychair.org \
    --cc=zsh-users@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).