unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Timothy Sample <samplet@ngyro.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: [ANN] Gash 0.1 released
Date: Sun, 02 Jun 2019 10:32:53 -0400	[thread overview]
Message-ID: <87tvd8rrai.fsf@ngyro.com> (raw)
In-Reply-To: <d9339188-d5c5-b9f3-f934-a34703843a3b@gmail.com> (Matt Wette's message of "Sun, 2 Jun 2019 06:21:15 -0700")

Hi Matt,

Matt Wette <matt.wette@gmail.com> writes:

> On 6/1/19 11:53 AM, Timothy Sample wrote:
>
>> Hi all,
>>
>> I am very pleased to announce that Gash version 0.1 has been released.
>
> Impressive.  Congrat's.

Thanks!

>>    http://download.savannah.nongnu.org/releases/gash/gash-0.1.tar.gz
>>
> When I run "make check" there are 8 XFAILs.  Are those expected?

Yes.  In Automake parlance, “XFAIL” is short for “eXpected FAILure”.

> PASS: tests/60-subst.sh
> XFAIL: tests/70-hash.sh
> XFAIL: tests/70-hash-hash.sh
> XFAIL: tests/70-percent.sh
> XFAIL: tests/70-percent-percent.sh
> XFAIL: tests/70-percent-space.sh
> XFAIL: tests/70-slash.sh
> XFAIL: tests/70-slash-string.sh
> XFAIL: tests/70-slash-string-slash.sh
> PASS: tests/100-cd.sh

These tests check a couple of fancier variable operator features, at
least one of which is Bash-specific.  We actually have patches to
implement the missing features required for these tests.  They need a
little work to be included, though.

Thanks for checking and following up!


-- Tim



  reply	other threads:[~2019-06-02 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-01 18:53 [ANN] Gash 0.1 released Timothy Sample
2019-06-01 19:43 ` Jeremy Korwin-Zmijowski
2019-06-02  8:07 ` ng0
2019-06-02 13:21 ` Matt Wette
2019-06-02 14:32   ` Timothy Sample [this message]
2019-06-02 16:08 ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tvd8rrai.fsf@ngyro.com \
    --to=samplet@ngyro.com \
    --cc=guile-user@gnu.org \
    --cc=matt.wette@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).