{"thread":{"id":"9454","subject":"git-rewrite-history behaves quite contrary to documentation","startedAt":"2007-08-09T11:30:26Z","lastAt":"2007-08-09T11:30:26Z","messageCount":1,"participants":["David Kastrup"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"50313","messageId":"86abt1j67h.fsf@lola.quinscape.zz","threadId":"9454","inReplyTo":null,"subject":"git-rewrite-history behaves quite contrary to documentation","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-08-09T11:30:26Z","receivedAt":"2007-08-09T11:30:26Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"\ngit-filter-branch --index-filter 'git-update-index --force-remove --remove -g bilder bilder3' master trunk\nRewrite a7a8f2fc263256c98ed5220e7467d34584c8c6ac (58/58)\nRef 'refs/heads/master' was rewritten\nRef 'refs/remotes/trunk' was rewritten\n\nThese refs were rewritten:\nfatal: Not a git repository: '/rep/akspiele/.git-rewrite/t/../../.git'\n\nThe manual page, however, claims:\n\n\n\t   git-filter-branch [--env-filter <command>] [--tree-filter <command>]\n\t\t\t [--index-filter <command>] [--parent-filter <command>]\n\t\t\t [--msg-filter <command>] [--commit-filter <command>]\n\t\t\t [--tag-name-filter <command>] [--subdirectory-filter <directory>]\n\t\t\t [-d <directory>] <new-branch-name> [<rev-list options>...]\n\n<new-branch-name> apparently is completely ignored: specifying a\nnon-existing branch will not work.\n\nIn the examples, it claims:\n\n\t   git filter-branch --index-filter 'git update-index --remove filename' newbranch\n\tNow, you will get the rewritten history saved in the branch\n\tnewbranch (your current branch is left untouched).\n\nThis is again wrong: one needs to write \"-g\" at very least, or it will\nnot bother removing a file that is not present in the working dir.\n\nCould someone please pass this on to Dscho?  He has me in his killfile.\n\n-- \nDavid Kastrup\n"}]}