IA64 bitkeeper trees (again)

From: Tony Luck <tony.luck_at_intel.com>
Date: 2004-08-19 08:09:38
After I posted my description of how I'm using Bitkeeper trees
to manage the ia64 part of Linux I got some feedback.  Len Brown
kindly talked me through how he runs a 2-phase/2-stage set of
trees for ACPI ... and after a while it began to make sense (the
layout of the trees, not ACPI :-).  So I've set up a similar set
of four trees:

          +--------------+     +-----------------+
          | test-2.6.9   |     | release-2.6.9   |
          +--------------+     +-----------------+
                  ^                     ^
                  |                     |
          +--------------+     +-----------------+
          | test- | ->  | release- |
          +--------------+     +-----------------+

Work begins at the bottom left, which is a clone of Linus's tree when he
applied the v2.6.8.1 label.  I apply patches there, and do whatever
compile/boot tests I need to make me feel comfortable about the patches.
I can then push/pull them up to the test-2.6.9 tree which is based on
Linus's latest (by pulling each day) and re-compile there to make sure
that the changes don't conflict with other changes to the base.  Andrew
Morton can then pull from the upper left tree to feed into "-mm"
expose the changes to a wider test audience.

Once the changes are suitably aged, I'll pull them over to the "release"
trees, which are the staging area for Linus to pull from.

The actual names all have "linux-ia64-" prepended.  E.g.


The names of the trees all change when Linus makes a release.

Len also gave me a script to create plain patches for non-BK
users ... I'll make the tweaks to the pathnames and get those
running soon.


To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Wed Aug 18 18:10:24 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:29 EST