All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aron Griffis <aron@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen-Devel <xen-devel@lists.xensource.com>,
	Hollis Blanchard <hollisb@us.ibm.com>,
	Tony Breeds <tony@bakeyournoodle.com>,
	Ewan Mellor <ewan@xensource.com>,
	XenPPC-devel <xen-ppc-devel@lists.xensource.com>,
	Dan Smith <danms@us.ibm.com>
Subject: Re: [XenPPC] Re: [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to support new architectures
Date: Tue, 3 Oct 2006 12:39:45 -0400	[thread overview]
Message-ID: <20061003163945.GC9217@fc.hp.com> (raw)
In-Reply-To: <C1484770.1F96%Keir.Fraser@cl.cam.ac.uk>

Keir Fraser wrote:  [Tue Oct 03 2006, 11:59:28AM EDT]
> Xen-unstable is currently a staging tree for xen-3.0.3-testing. Development
> is frozen until 3.0.3-0 is released.

Hi Keir,

Why are you doing it this way?  I thought a staging tree was somewhere
you could test builds prior to moving changesets to the live tree, so
you could yank the changesets, reset the staging tree, etc. without
affecting anybody.  Shouldn't there be a separate staging tree for
xen-3.0.3-testing?  Plus if xen-unstable is staging for
xen-3.0.3-testing, then it seems like branching was pointless.

Aron

  reply	other threads:[~2006-10-03 16:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29  9:56 [PATCH 0/6][TOOLS][XM-TEST] Update xm-test to support new architectures Tony Breeds
2006-09-29  9:56 ` [PATCH 1/6][TOOLS][XM-TEST] Update to use uClib buildroot-snapshot Tony Breeds
2006-09-29  9:56 ` [PATCH 2/6][TOOLS][XM-TEST] Remove hard coded reference to i386 Tony Breeds
2006-09-29  9:56 ` [PATCH 3/6][TOOLS][XM-TEST] rename buildroot -> buildroot-i386 Tony Breeds
2006-09-29  9:56 ` [PATCH 4/6][TOOLS][XM-TEST] Update .hgignore to remove artifacts of ramdisk build Tony Breeds
2006-09-29  9:56 ` [PATCH 5/6][TOOLS][XM-TEST] Refactor code to encapsulate architecture decisions in one place Tony Breeds
2006-09-29  9:57 ` [PATCH 6/6][TOOLS][XM-TEST] Add configuration data for powerpc Tony Breeds
2006-10-01 12:59   ` [XenPPC] " Jimi Xenidis
2006-10-02  5:37     ` Tony Breeds
2006-10-02 10:33       ` Jimi Xenidis
2006-10-02 14:11         ` Dan Smith
2006-10-02 14:43           ` Daniel Stekloff
2006-10-02 12:15 ` [XenPPC] [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to support new architectures Jimi Xenidis
2006-10-02 12:23 ` Ewan Mellor
2006-10-02 12:40   ` Jimi Xenidis
2006-10-02 14:14   ` Dan Smith
2006-10-02 15:02     ` Ewan Mellor
2006-10-02 15:08       ` [Xen-devel] " Jimi Xenidis
2006-10-02 15:52         ` Ewan Mellor
2006-10-02 20:01       ` Tony Breeds
2006-10-03 15:20   ` [XenPPC] " Hollis Blanchard
2006-10-03 15:30     ` Ewan Mellor
2006-10-03 15:53       ` Hollis Blanchard
2006-10-03 15:59         ` Keir Fraser
2006-10-03 16:39           ` Aron Griffis [this message]
2006-10-03 16:53             ` Keir Fraser
2006-10-02 14:46 ` [PATCH 0/6][TOOLS][XM-TEST] " Daniel Stekloff
2006-10-02 19:52   ` Tony Breeds

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=20061003163945.GC9217@fc.hp.com \
    --to=aron@hp.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=danms@us.ibm.com \
    --cc=ewan@xensource.com \
    --cc=hollisb@us.ibm.com \
    --cc=tony@bakeyournoodle.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ppc-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.