From: "Michael Paesold" <mpaesold@gmx.at>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
"Kamble, Nitin A" <nitin.a.kamble@intel.com>,
xen-devel@lists.xensource.com
Subject: Re: FW: [Xen-changelog] Added tag 3.0.2-branchedforchangesetd0d3fef37685be264a7f52201f8ef44c030daad3
Date: Wed, 5 Apr 2006 15:23:13 +0200 [thread overview]
Message-ID: <03e401c658b4$18a630a0$7801a8c0@zaphod> (raw)
In-Reply-To: A95E2296287EAD4EB592B5DEEFCE0E9D4BA101@liverpoolst.ad.cl.cam.ac.uk
Ian Pratt wrote:
> > Hi Keir,
> > What is the 3.0.2-breanched tag for?
>
> 3.0.2 has been forked from -unstable into -testing, where it is
> undergoing final testing before release.
>
> [I happen to know that the process got stalled because a regression has
> been detected, so the release won't happen today.]
I have noticed that the 3.0.2 release candidate tree/repository is obviously
not the one available as 3.0-testing on the XenSource website. Is it
available for public consumption anywhere? Guessing from some emails, I
think that you are applying bugfixes to that -testing repo, no? I would like
to test this rc before release, but without access to it, I am limited to
what is available in xen-unstable.
Best Regards,
Michael Paesold
next prev parent reply other threads:[~2006-04-05 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 21:39 FW: [Xen-changelog] Added tag 3.0.2-branched forchangesetd0d3fef37685be264a7f52201f8ef44c030daad3 Ian Pratt
2006-04-05 13:23 ` Michael Paesold [this message]
2006-04-05 13:36 ` FW: [Xen-changelog] Added tag 3.0.2-branchedforchangesetd0d3fef37685be264a7f52201f8ef44c030daad3 Keir Fraser
2006-04-05 13:51 ` FW: [Xen-changelog] Added tag3.0.2-branchedforchangesetd0d3fef37685be264a7f52201f8ef44c030daad3 Michael Paesold
-- strict thread matches above, loose matches on Subject: below --
2006-04-04 23:15 FW: [Xen-changelog] Added tag 3.0.2-branchedforchangesetd0d3fef37685be264a7f52201f8ef44c030daad3 James Harper
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='03e401c658b4$18a630a0$7801a8c0@zaphod' \
--to=mpaesold@gmx.at \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=nitin.a.kamble@intel.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.