From: Junio C Hamano <junkio@cox.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Pull from one branch to another?
Date: Wed, 28 Sep 2005 23:35:33 -0700 [thread overview]
Message-ID: <7vbr2cmle2.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <433B84BD.8030003@pobox.com> (Jeff Garzik's message of "Thu, 29 Sep 2005 02:07:57 -0400")
Jeff Garzik <jgarzik@pobox.com> writes:
> My question: is this the best/right way to pull one branch into
> another? It's been working for me, for months, but...
Yes, that is how 'resolve' is designed to work.
You could instead use standard 'git pull' from the local
repository. Here is what I usually do in git.git repository:
$ git checkout foo
$ ... work in foo "topic" branch
$ git checkout bar
$ ... work in bar "topic" branch
$ git checkout pu
$ git pull . foo bar
End result: foo and bar branches are pulled from the local
repository and merged into pu branch, as an Octopus.
Of course, I could instead:
$ git checkout pu
$ git pull . foo
$ git pull . bar
to pull 'foo' and then 'bar' in sequence, which is easier if
these topic branches touch overlapping area, because Octopus
does not allow manual resolving. On the other hand if I know
foo and bar are independent work, there is no point recording
the order of merges (merging foo first and then bar does not
have any significance) and I tend to let Octopus to happen.
next prev parent reply other threads:[~2005-09-29 6:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 6:07 Pull from one branch to another? Jeff Garzik
2005-09-29 6:35 ` Junio C Hamano [this message]
2005-09-29 6:54 ` Use of the -f flag on checkout Alan Chandler
2005-09-29 7:09 ` Matthias Urlichs
2005-09-29 9:02 ` Junio C Hamano
2005-09-29 7:06 ` Pull from one branch to another? Junio C Hamano
2005-09-29 17:52 ` Tony Luck
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=7vbr2cmle2.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jgarzik@pobox.com \
/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).