From: Matthias Fechner <idefix@fechner.net>
To: git@vger.kernel.org
Subject: Re: Switch from svn to git and modify repo completely
Date: Sun, 20 Nov 2011 23:21:06 +0100 [thread overview]
Message-ID: <4EC97D52.1010308@fechner.net> (raw)
In-Reply-To: <20111119225048.384189bc@zappedws>
Am 19.11.2011 19:50, schrieb Alexey Shumkin:
> take a look at "git filter-branch"
thanks a lot for your answer. I checked the manual page, but it does not
work like I expected it or it is described. What I did:
1. I searched the path name with the command:
git show --pretty="format:" --name-only firstrev..endrev | sort | uniq
|grep sdcc
2. I tried to remove the file with the command:
git filter-branch -f --tree-filter 'rm -f
software/tools/net.sourceforge.eclipsesdcc-1.0.0-win32.x86.zip'
--prune-empty -- --all
git told me:
Ref 'refs/heads/master' was rewritten
Ref 'refs/remotes/origin/master' was rewritten
WARNING: Ref 'refs/remotes/origin/master' is unchanged
3. I cloned the repository with:
git clone --no-hardlinks repo-orig.git repo-filtered.git
4. After this I verified in the repo-filtered.git that the file was
really completely removed, but it was not the case. I was able to
checkout the revision which holds the file.
Regarding the manual page it should work... but reality is different.
Has here anyone an idea what I did wrong?
Bye
Matthias
--
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
next prev parent reply other threads:[~2011-11-20 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 17:11 Switch from svn to git and modify repo completely Matthias Fechner
2011-11-19 18:50 ` Alexey Shumkin
2011-11-20 22:21 ` Matthias Fechner [this message]
2011-11-21 7:02 ` Jonathan Nieder
2011-11-27 10:56 ` Matthias Fechner
2011-11-28 10:10 ` Matthias Fechner
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=4EC97D52.1010308@fechner.net \
--to=idefix@fechner.net \
--cc=git@vger.kernel.org \
/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).