From: "Jean-François Burdet" <jfburdet@revelate.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Problem using git-filter-branch to move tree when repository name contains space
Date: Fri, 01 Apr 2011 23:49:04 +0200 [thread overview]
Message-ID: <4D964850.3050800@revelate.com> (raw)
In-Reply-To: <20110401144107.GA3103@sigill.intra.peff.net>
What you suggested solved my problem. What a fast answer ! 6minutes !
Thanks,
JF.
On 01.04.2011 16:41, Jeff King wrote:
> The problem is that GIT_INDEX_FILE is an absolute path that contains the
> repo name. So it needs to be quoted in the mv command. This should work:
>
> git filter-branch --index-filter \
> 'git ls-files -s | sed "s-\t\"*-&newsubdir/-" |
> GIT_INDEX_FILE=$GIT_INDEX_FILE.new \
> git update-index --index-info &&
> mv "$GIT_INDEX_FILE.new" "$GIT_INDEX_FILE"' HEAD
>
> -Peff
>
>
prev parent reply other threads:[~2011-04-01 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 14:30 Problem using git-filter-branch to move tree when repository name contains space Jean-François Burdet
2011-04-01 14:41 ` Jeff King
2011-04-01 14:46 ` [PATCH] docs: fix filter-branch subdir example for exotic repo names Jeff King
2011-04-01 21:49 ` Jean-François Burdet [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=4D964850.3050800@revelate.com \
--to=jfburdet@revelate.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 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).