From: Andreas Ericsson <ae@op5.se>
To: Brian Foster <brian.foster@innova-card.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
git mailing list <git@vger.kernel.org>
Subject: Re: [Q] merging from one (kernel) stable to another?
Date: Mon, 30 Mar 2009 15:52:21 +0200 [thread overview]
Message-ID: <49D0CE95.6020407@op5.se> (raw)
In-Reply-To: <200903301451.33956.brian.foster@innova-card.com>
Brian Foster wrote:
> On Monday 30 March 2009 14:19:11 Andreas Ericsson wrote:
>> Brian Foster wrote:
>
>>> (4) Tag the result `like-this';
>>> (5) Checkout our.21; and
>>> (6) Merge with `like-this'.
>> Merge is not necessary.
>
> <Shrugs/> I'll going to try in both ways (with and without
> merging) to better understand just what the results are like.
If you get the tree into the state you want and simply want to
connect the histories, you can do
git merge -s ours $other_branch
which will record the tree from the current commit as the tree
for the merge-commit (ie, all changes from $other_branch are
thrown away, and the merge always succeeds without conflicts).
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2009-03-30 13:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 8:24 [Q] merging from one (kernel) stable to another? Brian Foster
2009-03-30 9:33 ` Andreas Ericsson
2009-03-30 10:38 ` Johannes Sixt
2009-03-30 11:58 ` Brian Foster
2009-03-30 12:19 ` Johannes Sixt
2009-03-30 12:40 ` Brian Foster
2009-03-30 12:19 ` Andreas Ericsson
2009-03-30 12:51 ` Brian Foster
2009-03-30 13:52 ` Andreas Ericsson [this message]
2009-03-30 15:20 ` Ping Yin
2009-03-31 4:20 ` Kris Shannon
2009-03-30 17:31 ` Daniel Barkalow
2009-03-31 7:30 ` Brian Foster
2009-03-30 18:23 ` Uwe Kleine-König
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=49D0CE95.6020407@op5.se \
--to=ae@op5.se \
--cc=brian.foster@innova-card.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).