summaryrefslogtreecommitdiff
path: root/test/1_flat
diff options
context:
space:
mode:
authoruckelman <uckelman@nomic.net>2010-11-02 21:36:46 +0000
committeruckelman <uckelman@nomic.net>2010-11-02 21:36:46 +0000
commit4f45cd4aa100122e0bac25e4ff2208a8bf4d53cf (patch)
treeb28856737c04d540fd7f947ab30c260945c8ba5f /test/1_flat
parentcb5ffae7c9c93513f2fa88a059292c7d37761ae4 (diff)
Added test messages and attachments.
git-svn-id: https://vassalengine.svn.sourceforge.net/svnroot/vassalengine/site-src/trunk@7437 67b53d14-2c14-4ace-a08f-0dab2b34000c
Diffstat (limited to 'test/1_flat')
-rw-r--r--test/1_flat27
1 files changed, 27 insertions, 0 deletions
diff --git a/test/1_flat b/test/1_flat
new file mode 100644
index 0000000..711cc8d
--- /dev/null
+++ b/test/1_flat
@@ -0,0 +1,27 @@
+Thus spake "wlk":
+>
+> uckelman wrote:
+> > How close are you guys to a 3.1-compatble release, BTW? We've had at least
+> > one bug report every day since the release of 3.1.0 about VASL being
+> > incompatible with 3.1...
+>
+>
+> Actually, I fixed like 5 bugs now, and there's none left I am aware of, at le
+> ast the ones related to VASL binaries.
+> I'm daily using 5.9 with 3.1.13 and didn't notice anything wrong.
+> We were waiting for 3.1.14 to be released to publish VASL 5.9.
+>
+
+Oh! I didn't know you were waiting for 3.1.14. I can put together a test
+build tonight, and if people try it out to confirm that it's ok, we can
+release tomorrow.
+
+--
+J.
+
+_______________________________________________
+Messages mailing list
+Messages@forums.vassalengine.org
+http://forums.vassalengine.org/mailman/listinfo/messages_forums.vassalengine.org
+
+