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: Sat, 10 Dec 2011 08:45:31 -0600	[thread overview]
Message-ID: <20111210144531.GA3616@linux1> (raw)
In-Reply-To: <4EE25814.1000308@gentoo.org>

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

On Fri, Dec 09, 2011 at 07:48:52PM +0100, Sebastian Pipping wrote:
> On 12/09/2011 05:16 PM, William Hubbs wrote:
> >  Yes, I saw it, but it doesn't seem to do what we want. It merges the
> >  branches together instead of swapping them.
> 
> Maybe it's not what _you_ want, but it does
> 
>  - make catalyst_2 content appear on master
> 
>  - doesn't break fast forward "git pull" for anyone
> 
>  - supports branching catalyst_2 off master, too

The method you are suggesting does _NOT_ make the current content of
master appear on catalyst_3, which is the other part of what releng is
requesting.

What I think I can do, but I'm not quite sure how to do it, is:

1) create a catalyst_3 branch at the same point in history where
catalyst_2 was created. I believe I can accomplish this with

git branch catalyst_3 $(git merge-base master catalyst_2)

2) put the code on master that is _NOT_ on catalyst_2 on catalyst_3.

Any suggestions for how to do this?

3) put the code on catalyst_2 on master.

What about this?

William


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

  reply	other threads:[~2011-12-10 14:50 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
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 [this message]
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=20111210144531.GA3616@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