From: Keir Fraser <keir.xen@gmail.com>
To: Matt Wilson <msw@amazon.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [ANNOUNCE] Final release candidate for Xen 4.2.0
Date: Thu, 13 Sep 2012 17:52:42 +0100 [thread overview]
Message-ID: <CC77CDEA.3EB45%keir.xen@gmail.com> (raw)
In-Reply-To: <20120913092503.GA15042@u002268147cd4502c336d.ant.amazon.com>
On 13/09/2012 17:25, "Matt Wilson" <msw@amazon.com> wrote:
> On Thu, Sep 13, 2012 at 03:53:28PM +0100, Ian Jackson wrote:
>>> We plan to call the 4.2.0 release on Monday, with no further modifications.
>>> So please test this "GA preview"!
>>
>> As Keir says. If all goes well the 4.2.0 release will have a
>> functionally identical tarball.
>
> Any chance my man page fixes will make it in to the final tarball?
> "Functionally identical" seems to leave some wiggle room.
I think these are low priority enough they can wait for 4.2.1, which will be
6-8 weeks.
-- Keir
> xmdomain.cfg.5 has POD errors (displayed when you run "man xmdomain.cfg":
> POD ERRORS
> Hey! The above document had some coding errors, which are
> explained
> below:
>
> Around line 301:
> You can't have =items (as at line 305) unless the first
> thing after
> the =over is an =item
>
> Around line 311:
> '=item' outside of any '=over'
>
> xl.cfg.5 has POD errors:
> POD ERRORS
> Hey! The above document had some coding errors, which are
> explained
> below:
>
> Around line 405:
> '=item' outside of any '=over'
>
> Around line 429:
> You forgot a '=back' before '=head2'
>
> Around line 687:
> '=item' outside of any '=over'
>
> Around line 695:
> You forgot a '=back' before '=head3'
>
> Matt
prev parent reply other threads:[~2012-09-13 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 11:34 [ANNOUNCE] Final release candidate for Xen 4.2.0 Keir Fraser
2012-09-13 14:53 ` Ian Jackson
2012-09-13 16:25 ` Matt Wilson
2012-09-13 16:52 ` Keir Fraser [this message]
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=CC77CDEA.3EB45%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=msw@amazon.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).