git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: FusionX86 <fusionx86@gmail.com>
To: Git <git@vger.kernel.org>
Subject: git p4 rebase --branch
Date: Thu, 21 May 2015 18:52:52 -0600	[thread overview]
Message-ID: <CAFcBi8-eH=td7478oPu5iPn9q1RGBFJ+NNLYHQid2xaF5T1sdg@mail.gmail.com> (raw)

For my Perforce to Git migration project, I am creating an empty local
git repo and then running git p4 sync with --branch to bring code from
Perforce into a specific Git branch. I'm going this route because I
need to take two Perforce branches that are similar and put them into
different branches of the same Git repo. One will go into dev and one
in master.

This seems to be working for me so far, but I want to use rebase to
pull new changes in and just realized that --branch isn't a supported
option for rebase. Any way to use git p4 rebase and target a local git
branch other than master?

                 reply	other threads:[~2015-05-22  0:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAFcBi8-eH=td7478oPu5iPn9q1RGBFJ+NNLYHQid2xaF5T1sdg@mail.gmail.com' \
    --to=fusionx86@gmail.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).