All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] STABLE cluster branch?!
Date: Wed, 12 Sep 2007 10:27:40 -0500	[thread overview]
Message-ID: <20070912152740.GA3406@redhat.com> (raw)
In-Reply-To: <1189610290.24044.64.camel@marc>

On Wed, Sep 12, 2007 at 05:18:10PM +0200, Marc - A. Dahlhaus [ Administration | Westermann GmbH ] wrote:
> I think a separate branch which follows the last released vanilla kernel
> tree for gfs2 could be useful while there is so much movement in HEAD.
> Merging HEAD into that branch after each merge window on Linus tree
> could minimize the needed manpower and the release of tarballs would
> also require less time out of that branch. Adopters of the tarball could
> get fixes from there too. Before gfs2 the STABLE branch was exactly that
> or wasn't it?

You have a good point, we've been talking about creating a STABLE2 branch
that's equivalent to the RHEL5 branch except follows upstream kernels.
(Same way the RHEL4/STABLE branches worked.) We're hoping to wait a while
longer before doing that, though.  A little more discipline about what's
checked into HEAD will make HEAD as effective (for now) as STABLE2.

Dave



      reply	other threads:[~2007-09-12 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11  9:04 [Cluster-devel] STABLE cluster branch?! Marc
2007-09-11 16:48 ` David Teigland
2007-09-12 10:12   ` Marc
2007-09-12 14:05     ` David Teigland
2007-09-12 15:18       ` Marc
2007-09-12 15:27         ` David Teigland [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=20070912152740.GA3406@redhat.com \
    --to=teigland@redhat.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.