From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] rfc: merging catalyst git branches
Date: Fri, 09 Dec 2011 00:55:38 -0100 [thread overview]
Message-ID: <4EE16A9A.4090609@gentoo.org> (raw)
In-Reply-To: <20111208194623.GA2416@linux1>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08-12-2011 18:46, William Hubbs wrote:
> 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,
I'd rather not lose the work for catalyst_3. I understand and agree we
use the catalyst_2 branch for our releases, so I'd rather move master
to a new branch, call it catalyst_3, experimental or something else,
and then make catalyst_2 as master.
> William
>
- --
Regards,
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJO4WqaAAoJEC8ZTXQF1qEPfQwQALbl7ut059PYHqMZFFmKyjy7
Y7PMRB1UroTVOA3atyo2abGZ9PmL34Gh2ns1SF2LxXSP2TlUuSTzswTlEvPj9Stc
zsmcfxH+OpKAykgV1UJjc6PTuarlGRihmOES2ezLSneoKxvvSXbIH37wqGFOCld/
bzaFjBL/TCvfXZIeXngHQ9SXIdEp9IWKlL14/WGmiP2iKeHPZ8O4j0k/OL8h1Nvx
BTD83F1UruELkWkLQz7F/yGW64AFH5EzIC4ebnA9NMv6KhsF5G2VDfwEKuJwgCAe
XE8Jt9IdEDX9akOflHlCLo7iwPyMsssGqXUo53b/uThOusRZkSvNG0+jVOvTL4oh
387VFXo3cNKPyQns/EQQml2jF2MNCqbHVEeW/s3IzQg6NGT3JNu5wjHTJz1hcaqs
rcb54+F/jwhd1J4s+xXKuU0sJAJvmFGneHfCnPs+EMXLS2mGw1YNu4+FlKwLwdQN
FTYhUB/kyFHM/c2MGTO2V/M3dt5efu5tgaF1QqCfsOQiR2dXIGkHqStLqZHHfK2J
Ets+epXt3iGIN0udKIEWSqaAwKQW40RstbWlEcUT2TD0GBjW+ln5oU/d4KkvS2rn
IBfN+19hW2OFt0KYo+Bc2GTYCRIPaRYDikyib4ZnzKhSnGKMjxPGYiczmgDIcvr8
FQwNtsOccSDK69tD49FQ
=96Ty
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-12-09 1:56 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
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 [this message]
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=4EE16A9A.4090609@gentoo.org \
--to=jmbsvicetto@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