public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] rfc: merging catalyst git branches
Date: Thu, 8 Dec 2011 13:46:23 -0600	[thread overview]
Message-ID: <20111208194623.GA2416@linux1> (raw)
In-Reply-To: <20110627044433.GA9772@linux1>

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

On Sun, Jun 26, 2011 at 11:44:33PM -0500, William Hubbs wrote:
> All,
> 
> this has been mentioned in a couple of threads, so I want to bring it up
> in a separate thread so that we can keep the discussions organized. :-)
> 
> As you know, catalyst has two branches in its git repository, master,
> which was going to be catalyst 3.0, and a branch called catalyst_2 which
> is the branch being used by releng for official releases.
> 
> We know from what Jorge said that the master branch is broken.
> 
> Right now, we are commiting changes to both branches, but that is not a
> good idea over the long term. We need to figure out if we should keep
> master and try to release 3.0 from there at some point.  If that is what
> we want to do, we need to go through the catalyst_2 branch and port
> relevant commits to master.
> 
> If we are not interested in the 3.0 code, we should probably find a way
> to revert all of it from master with one commit then rebase the 2.0
> branch on master and move it back there.

If no one objects, I will look into doing this next week; the catalyst_2
code should move to master since there doesn't appear to be any work
going on for releasing catalyst 3.

Comments?

William


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-12-08 20:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27  4:44 [gentoo-catalyst] rfc: merging catalyst git branches William Hubbs
2011-12-08 19:46 ` William Hubbs [this message]
2011-12-08 20:31   ` Sebastian Pipping
2011-12-08 21:42     ` William Hubbs
2011-12-08 23:43       ` Sebastian Pipping
2011-12-09  1:55   ` Jorge Manuel B. S. Vicetto
2011-12-09  2:56     ` Sebastian Pipping
2011-12-09  3:19     ` William Hubbs
2011-12-09  4:42       ` Sebastian Pipping
2011-12-09 16:16         ` William Hubbs
2011-12-09 17:37           ` Matt Turner
2011-12-09 18:38             ` Sebastian Pipping
2011-12-09 18:48           ` Sebastian Pipping
2011-12-10 14:45             ` William Hubbs
2011-12-10 22:15               ` Sebastian Pipping
2011-12-11  0:35                 ` Peter Stuge
2012-06-24 23:33                 ` Sebastian Pipping
2012-06-25  4:04                   ` Matt Turner
2012-07-02 14:55                     ` Sebastian Pipping
2012-07-02 21:00                       ` Matt Turner

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=20111208194623.GA2416@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-catalyst@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox