From: Avery Pennarun <apenwarr@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: JörgenHägg <jorgen.hagg@axis.com>, git@vger.kernel.org
Subject: Re: Copying files and keeping the history
Date: Thu, 11 Jun 2009 23:44:15 -0400 [thread overview]
Message-ID: <32541b130906112044m7cf2c0e9s2ba4815a31e534a@mail.gmail.com> (raw)
In-Reply-To: <fabb9a1e0906111129x53a6d90p15a97d958a2d2f63@mail.gmail.com>
On Thu, Jun 11, 2009 at 2:29 PM, Sverre Rabbelier<srabbelier@gmail.com> wrote:
> On Thu, Jun 11, 2009 at 15:20, JörgenHägg<jorgen.hagg@axis.com> wrote:
>> Is this somehow possible?
>
> Try git filter-branch to get just the commits you want and nudge them
> to contain what you want (do this in a seperate branch/copy of
> repository A). When you're done, pull the branch into B and merge it.
> Instant win?
You could also consider 'git subtree'
(http://github.com/apenwarr/git-subtree) to merge the other tree
(including its history) in as a subdirectory.
Avery
prev parent reply other threads:[~2009-06-12 3:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 13:20 Copying files and keeping the history JörgenHägg
2009-06-11 18:29 ` Sverre Rabbelier
2009-06-12 3:44 ` Avery Pennarun [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=32541b130906112044m7cf2c0e9s2ba4815a31e534a@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=jorgen.hagg@axis.com \
--cc=srabbelier@gmail.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).