From: Jeff King <peff@peff.net>
To: Nick Andrew <nick@nick-andrew.net>
Cc: luisgutz <luis@xmos.com>, git@vger.kernel.org
Subject: Re: copy selected history between repostories
Date: Fri, 18 Jul 2008 21:21:07 -0400 [thread overview]
Message-ID: <20080719012107.GA14068@sigill.intra.peff.net> (raw)
In-Reply-To: <20080719010122.GA12047@mail.local.tull.net>
On Sat, Jul 19, 2008 at 11:01:22AM +1000, Nick Andrew wrote:
> I couldn't figure out git-filter-branch, so I did the following,
> which worked for me:
>
> First, export commits as patches in mbox format:
>
> git log -p --first-parent --reverse --pretty=email $* > mbox
> [...]
>
> Finally, import into new repo:
>
> git-am mbox2
Note that this will lose any interesting history topology you had, like
branching and merging (and it may have trouble applying all patches in
that case, too). But if your history was a straight line, it should
produce equivalent results.
-Peff
prev parent reply other threads:[~2008-07-19 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 16:58 copy selected history between repostories luisgutz
2008-07-18 17:12 ` Avery Pennarun
2008-07-19 1:01 ` Nick Andrew
2008-07-19 1:12 ` Johannes Schindelin
2008-07-19 1:21 ` 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=20080719012107.GA14068@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=luis@xmos.com \
--cc=nick@nick-andrew.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).