From: Alex Elder <aelder@sgi.com>
To: XFS Mailing List <xfs@oss.sgi.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [ANNOUNCE] xfstests v1.1.0
Date: Fri, 14 Oct 2011 09:29:35 -0500 [thread overview]
Message-ID: <1318602575.3827.18.camel@doink> (raw)
Version 1.1.0 of xfstests has been released.
The source code can be accessed via git using this URL:
git://oss.sgi.com/xfs/cmds/xfstests.git
The development tree for this code (not available at
the moment) is normally published here as well:
git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
This is the first tagged version of xfstests. Future
versioned releases will be marked occasionally, more
or less frequently as conditions dictate.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Alex Elder <aelder@sgi.com>
To: XFS Mailing List <xfs@oss.sgi.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [ANNOUNCE] xfstests v1.1.0
Date: Fri, 14 Oct 2011 09:29:35 -0500 [thread overview]
Message-ID: <1318602575.3827.18.camel@doink> (raw)
Version 1.1.0 of xfstests has been released.
The source code can be accessed via git using this URL:
git://oss.sgi.com/xfs/cmds/xfstests.git
The development tree for this code (not available at
the moment) is normally published here as well:
git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
This is the first tagged version of xfstests. Future
versioned releases will be marked occasionally, more
or less frequently as conditions dictate.
-Alex
next reply other threads:[~2011-10-14 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 14:29 Alex Elder [this message]
2011-10-14 14:29 ` [ANNOUNCE] xfstests v1.1.0 Alex Elder
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=1318602575.3827.18.camel@doink \
--to=aelder@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.