All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <keir@xensource.com>
Cc: John Hannfield <hal9020@gmail.com>, xen-devel@lists.xensource.com
Subject: Re: 2.6.18 kernel status
Date: Tue, 6 Mar 2007 17:19:52 +0000	[thread overview]
Message-ID: <20070306171952.GK29872@redhat.com> (raw)
In-Reply-To: <C212F2D6.AAD4%keir@xensource.com>

On Tue, Mar 06, 2007 at 10:28:38AM +0000, Keir Fraser wrote:
> 
> On 5/3/07 23:53, "John Hannfield" <hal9020@gmail.com> wrote:
> 
> > I am just trying out the 2.6.18 kernel in xen-unstable.hg , but on doing a
> > make linux-2.6-xen0-build I'm getting to the following error.
> 
> This is fixed but the patch is stuck in our staging tree until regression
> tests pass.

How about making your staging tree publically viewable so people get better
visibility into whether patches sent to xen-devel have been picked up and
integrated into the tree ? Sure, we don't want people to be actually working
against a staging tree, but I think being able to see what's coming along
in the staging tree would be good for transparency / communications with
the non-XenSource people whom are posting patches. 

In this particular instance it would also allow for end-user testing of
the aforementioned kernel patch in parallel with the automated tests,
rather than serializing the test proces.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  parent reply	other threads:[~2007-03-06 17:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05 23:53 2.6.18 kernel status John Hannfield
2007-03-06 10:28 ` Keir Fraser
2007-03-06 13:52   ` John Hannfield
2007-03-06 14:46     ` Mark Williamson
2007-03-06 17:13       ` John Hannfield
2007-03-06 17:44         ` Mark Williamson
2007-03-06 17:48           ` Ian Campbell
2007-03-06 17:19   ` Daniel P. Berrange [this message]
2007-03-06 17:29     ` Petersson, Mats
2007-03-06 17:37     ` Ian Pratt
2007-03-06 17:40       ` Daniel P. Berrange

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=20070306171952.GK29872@redhat.com \
    --to=berrange@redhat.com \
    --cc=hal9020@gmail.com \
    --cc=keir@xensource.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.