From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Subject: git-rewrite-history behaves quite contrary to documentation
Date: Thu, 09 Aug 2007 13:30:26 +0200 [thread overview]
Message-ID: <86abt1j67h.fsf@lola.quinscape.zz> (raw)
git-filter-branch --index-filter 'git-update-index --force-remove --remove -g bilder bilder3' master trunk
Rewrite a7a8f2fc263256c98ed5220e7467d34584c8c6ac (58/58)
Ref 'refs/heads/master' was rewritten
Ref 'refs/remotes/trunk' was rewritten
These refs were rewritten:
fatal: Not a git repository: '/rep/akspiele/.git-rewrite/t/../../.git'
The manual page, however, claims:
git-filter-branch [--env-filter <command>] [--tree-filter <command>]
[--index-filter <command>] [--parent-filter <command>]
[--msg-filter <command>] [--commit-filter <command>]
[--tag-name-filter <command>] [--subdirectory-filter <directory>]
[-d <directory>] <new-branch-name> [<rev-list options>...]
<new-branch-name> apparently is completely ignored: specifying a
non-existing branch will not work.
In the examples, it claims:
git filter-branch --index-filter 'git update-index --remove filename' newbranch
Now, you will get the rewritten history saved in the branch
newbranch (your current branch is left untouched).
This is again wrong: one needs to write "-g" at very least, or it will
not bother removing a file that is not present in the working dir.
Could someone please pass this on to Dscho? He has me in his killfile.
--
David Kastrup
reply other threads:[~2007-08-09 11:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=86abt1j67h.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--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