From: Pierre Habouzit <madcoder@debian.org>
To: Xavier Maillard <zedek@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: What's the best method between merging and rebasing ?
Date: Mon, 12 Mar 2007 13:08:20 +0100 [thread overview]
Message-ID: <20070312120820.GE18952@mad.intersec.eu> (raw)
In-Reply-To: <200703121139.l2CBdcUL022906@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]
On Mon, Mar 12, 2007 at 12:39:38PM +0100, Xavier Maillard wrote:
> Hi,
>
> Say I have a project in this state:
>
> orig master -> A -> B -> C -> HEAD
>
> I want to make A diverging from the original branch so I would be
> at this state :
>
> orig master -> A -> B -> C -> HEAD
> \
> -> D -> E -> F ->
>
> I want master to be at HEAD of the new branch and I want to pick
> commits here and there from the original master branch.
I'm not sure I get this right, but if I understand you correctly, I'd
say that you could branch your master into a old-master branch.
then delete the master branch, and branch it again from the "orig
master", then cherry pick from old-master what you want to keep.
Of course those approachs only "work" if nobody clones your
repository, as you will rewrite history with that.
But Maybe I missed what you want to achieve :)
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-12 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 11:39 What's the best method between merging and rebasing ? Xavier Maillard
2007-03-12 12:08 ` Pierre Habouzit [this message]
2007-03-12 16:34 ` Xavier Maillard
2007-03-12 17:11 ` Johannes Sixt
2007-03-12 19:43 ` Pierre Habouzit
2007-03-12 17:37 ` Pierre Habouzit
2007-03-12 19:14 ` Xavier Maillard
2007-03-12 19:42 ` Pierre Habouzit
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=20070312120820.GE18952@mad.intersec.eu \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=zedek@gnu.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;
as well as URLs for NNTP newsgroup(s).