From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] preparing for 0.7
Date: Mon, 16 Mar 2009 10:27:48 -0700 [thread overview]
Message-ID: <1237224356-sup-1941@entry> (raw)
Hi all,
I've prepared master for an 0.7 release. If you get a chance, please try
it out and let me know if there's anything obviously broken. The changes
I'm most excited about are the Ferret locking (so hopefully no more
index corruption) and being able to type long answers to Sup's
questions.
--
William <wmorgan-sup at masanjin.net>
next reply other threads:[~2009-03-16 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 17:27 William Morgan [this message]
2009-03-17 18:29 ` Mark Alexander
2009-03-18 13:49 ` William Morgan
2009-03-18 15:39 ` Lee Hinman
2009-03-19 17:02 ` William Morgan
2009-03-18 21:11 ` Mark Alexander
2009-03-19 19:18 ` Mark Alexander
2009-03-19 19:25 ` William Morgan
2009-03-19 20:41 ` Mark Alexander
2009-04-15 17:29 ` [sup-talk] Lost Maildir Messages Iain
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=1237224356-sup-1941@entry \
--to=wmorgan-sup@masanjin.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