From: Ben Guthro <bguthro@virtualiron.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: 3.1.1 release tag in staging
Date: Wed, 10 Oct 2007 09:56:17 -0400 [thread overview]
Message-ID: <470CDA01.1080003@virtualiron.com> (raw)
I noticed the 3.1.1 release tag went into staging today - so I can only
assume this will propagate to main-line shortly. Congratulations on the
release - it seems pretty stable in my testing.
Browsing through the 422 changesets - I realize that many changesets
were pulled in as prerequisites for other, more major cs's.
So now that this is out - is there a general summary in what major bugs
were addressed in the 422 changesets that have been put into this point
release?
(A 0.0.1 change seems to indicate a minor upgrade - but in fact, 422
non-trivial patches is a fair amount of churn.)
Ben
next reply other threads:[~2007-10-10 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 13:56 Ben Guthro [this message]
2007-10-10 14:37 ` 3.1.1 release tag in staging Keir Fraser
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=470CDA01.1080003@virtualiron.com \
--to=bguthro@virtualiron.com \
--cc=xen-devel@lists.xensource.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.