From: Jeff Garzik <jgarzik@pobox.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Pull from one branch to another?
Date: Thu, 29 Sep 2005 02:07:57 -0400 [thread overview]
Message-ID: <433B84BD.8030003@pobox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
I currently use the attached script to merge the contents of one branch
into another branch, in my kernel trees:
$ cd /repo/netdev-2.6
$ git checkout -f sky2
$ ... merge patches ...
$ git checkout -f upstream
$ ... merge more patches ...
$ git checkout -f ALL
$ git-pull-branch upstream
$ git-pull-branch sky2
End result: 'ALL' branch contains everything in 'sky2' and 'upstream'
branches. I use the above for creating an all-inclusive branch that
users can test, and that Andrew Morton can pull into his -mm kernel tree.
Right now, my git-pull-branch script (attached) simply calls
git-resolve-script, which nicely skips the fetch step and any
complications related to that.
My question: is this the best/right way to pull one branch into
another? It's been working for me, for months, but...
Jeff
[-- Attachment #2: git-pull-branch --]
[-- Type: text/plain, Size: 59 bytes --]
#!/bin/sh
git-resolve-script HEAD $1 "`pwd` branch '$1'"
next reply other threads:[~2005-09-29 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 6:07 Jeff Garzik [this message]
2005-09-29 6:35 ` Pull from one branch to another? Junio C Hamano
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=433B84BD.8030003@pobox.com \
--to=jgarzik@pobox.com \
--cc=git@vger.kernel.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).