From: Jeff King <peff@peff.net>
To: Ryan <duderino.lebowski@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Getting Commits from One Repository to Another
Date: Fri, 22 May 2009 03:26:06 -0400 [thread overview]
Message-ID: <20090522072606.GA1409@coredump.intra.peff.net> (raw)
In-Reply-To: <loom.20090521T200115-589@post.gmane.org>
On Thu, May 21, 2009 at 08:08:01PM +0000, Ryan wrote:
> Thanks to both of you for your help. I tried Peff's suggestion last
> night, and could not get it to work. Matthieu is correct that the
> public repo was not a clone but a fresh import. Furthermore, I
> discovered that work had been done between the last pull from private
> the the import into public. (Ugh!)
Ah, OK, I missed that when reading your initial report. Matthieu's
suggestion is the correct one, then.
> Anyway, before I saw Matthieu's post (away from internet, which is so
> rare these days), I managed to succeed by using git format-patch on
> the commits that I needed, and then used git am on the private repo.
> There was one conflict, but I was able to resolve it.
>
> Hopefully I'm not faced with this problem again, but if so, I'll try
> Mattieu's suggestion.
Actually, you will find that "git rebase" is basically "format-patch |
am" under the hood, so you more or less did the same thing (but calling
rebase probably would have been a little more convenient).
-Peff
prev parent reply other threads:[~2009-05-22 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 23:37 Getting Commits from One Repository to Another Big Lebowski
2009-05-21 4:04 ` Jeff King
2009-05-21 9:12 ` Matthieu Moy
2009-05-21 20:08 ` Ryan
2009-05-22 7:26 ` Jeff King [this message]
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=20090522072606.GA1409@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=duderino.lebowski@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).