mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Solar Designer <solar@openwall.com>
To: musl@lists.openwall.com
Subject: Re: Revitalizing testing!
Date: Wed, 26 Oct 2011 11:41:21 +0400	[thread overview]
Message-ID: <20111026074121.GE2943@openwall.com> (raw)
In-Reply-To: <20111023212545.GD132@brightrain.aerifal.cx>

Hi Rich,

On Sun, Oct 23, 2011 at 05:25:45PM -0400, Rich Felker wrote:
> Since GSoC ended with some partial successes on Luka's libc testing
> project "cluts", I'd like to look towards picking up testing where
> that left off and "finishing" cluts.

I just wanted to let you know that this sounds great to me.

Thank you for posting this!

Alexander


  parent reply	other threads:[~2011-10-26  7:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-23 21:25 Rich Felker
2011-10-23 23:52 ` Rich Felker
2011-10-26  7:41 ` Solar Designer [this message]
2011-10-27  1:51 ` Luka Marčetić

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=20111026074121.GE2943@openwall.com \
    --to=solar@openwall.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

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

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