From: Dave Jones <davej@redhat.com>
To: trinity@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Trinity 1.3.
Date: Fri, 20 Dec 2013 14:50:10 -0500 [thread overview]
Message-ID: <20131220195010.GA10605@redhat.com> (raw)
I just tagged and pushed out a tarball for 1.3, because it's been six months since
the last one, and the recent work on fuzzing mmaps seems to have reached a good
place to stop before I move onto the next set of changes.
[read as: so people can use 1.3 to continue breaking the VM while I potentially
break things in trinity for a while]
Ideas for further improvements in this, or other areas always welcomed.
Tarball: http://codemonkey.org.uk/projects/trinity/trinity-1.3.tgz
git: git://git.codemonkey.org.uk/trinity
thanks,
Dave
reply other threads:[~2013-12-20 19:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131220195010.GA10605@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trinity@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox