From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: Re: Moving a directory with history from one repository to another while renaming
Date: Thu, 21 Jun 2007 14:57:28 +0100 [thread overview]
Message-ID: <200706211457.29030.andyparkins@gmail.com> (raw)
In-Reply-To: <20070621130137.GB4487@coredump.intra.peff.net>
On Thursday 2007 June 21, Jeff King wrote:
> You can do this much more efficiently by just operating on the index.
> Something like:
>
> git-filter-branch --index-filter \
> 'git-ls-files -s | sed -n 's/change/paths/p' | git-update-index
> --index-info' \ directorymoved
:-D Even better. I am definitely in the "fan of git-filter-branch" camp.
Thanks for sharing that line; I've actually found it instructive for more than
just git-filter-branch. I definitely hadn't appreciated the fact that the
index can be so easily manipulated.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-06-21 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 12:37 Moving a directory with history from one repository to another while renaming Andy Parkins
2007-06-21 13:01 ` Jeff King
2007-06-21 13:57 ` Andy Parkins [this message]
2007-06-21 14:05 ` Johannes Schindelin
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=200706211457.29030.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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 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.