public inbox for mauve-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Mario Torre <neugens@limasoftware.net>
Cc: mauve-patches <mauve-patches@sources.redhat.com>
Subject: Re: FYI: Sound test
Date: Fri, 06 Jul 2007 08:42:00 -0000	[thread overview]
Message-ID: <1183711313.3651.38.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <1183676447.3448.6.camel@nirvana.limasoftware.net>

On Fri, 2007-07-06 at 01:00 +0200, Mario Torre wrote:
> I'm going to commit this patch that adds a mauve test for the Sound API.
> 
> The patch shown below is not the full commit, because it obviously lacks
> the binary audio file.
> 
> The wave file comes from the k3b package from fedora 7

Nice. Could you also add a little note to the README file about where
the files in gnu/testlet/javax/sound/sampled/data came from? That way it
is a little easier for people to find where each file came from (since
datafiles don't have a boilerplate header and not everybody goes through
the whole ChangeLog file).

Thanks,

Mark

      reply	other threads:[~2007-07-06  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05 23:02 Mario Torre
2007-07-06  8:42 ` Mark Wielaard [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=1183711313.3651.38.camel@dijkstra.wildebeest.org \
    --to=mark@klomp.org \
    --cc=mauve-patches@sources.redhat.com \
    --cc=neugens@limasoftware.net \
    /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).