From: Jakub Narebski <jnareb@gmail.com>
To: Ben Walton <bwalton@artsci.utoronto.ca>
Cc: Alan Edwards <kae@xnet.com>, git <git@vger.kernel.org>
Subject: Re: How to reorganize git tree
Date: Thu, 26 Jan 2012 15:27:32 -0800 (PST) [thread overview]
Message-ID: <m3ehumdoxs.fsf@localhost.localdomain> (raw)
In-Reply-To: <1327604128-sup-1697@pinkfloyd.chass.utoronto.ca>
Ben Walton <bwalton@artsci.utoronto.ca> writes:
> Excerpts from Alan Edwards's message of Thu Jan 26 13:35:05 -0500 2012:
>
> Hi Alan,
>
> > Any one have any suggestions?
>
> I think that git filter-branch is going to be your friend here. I
> won't prescribe the details as you should definitely read and
> understand the docs for this one, but things like
> --subdirectory-filter and/or --tree-filter will be of great use to
> you, I think.
Third-party git-subtree tool can also help here, I think.
--
Jakub Narebski
prev parent reply other threads:[~2012-01-26 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 18:35 How to reorganize git tree Alan Edwards
2012-01-26 18:57 ` Ben Walton
2012-01-26 23:27 ` Jakub Narebski [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=m3ehumdoxs.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=bwalton@artsci.utoronto.ca \
--cc=git@vger.kernel.org \
--cc=kae@xnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.