On Wed, Jul 16, 2014 at 12:11:49AM -0700, cemico wrote: > 1. Sorry, i don't really understand what the question is. What does > rebasing and marking with "e" mean? Is it possible to achieve > what i want with that rebasing and "e"ing?
Using `git rebase -i` you can do changes to history manually. That doesn't really scale to even a small repo like your though. For instance, to modify the latest changeset run `git rebase -i HEAD^`, then read the instructions as the editor pops up and then replace 'pick' with 'e' (or 'edit') for the changeset. Save the file and exit the editor. When your done making your changes you just commit and then run `git rebase --continue`. Of course you do this on a backup of your repo :) (The stuff above is from memory so please read the full help for `git rebase` before blaming me for any misinformation. ;) > 2. We did this: > > git filter-branch --index-filter 'git rm -rf --cached --ignore-unmatch > DIRECTORY/' --prune-empty --tag-name-filter cat -- --all > > and afterwards: > > rm -rf .git/refs/original/ && git reflog expire --all && git gc --aggressive > --prune > > That did not help, so we tried: > http://dound.com/2009/04/git-forever-remove-files-or-folders-from-history/ > http://rtyley.github.io/bfg-repo-cleaner/ > http://git-scm.com/book/en/Git-Tools-Rewriting-History#The-Nuclear-Option:-filter-branch > > with no effort I've done exactly that sort of thing in the past, using the same sources for information, so what is it that does happen when running the command above? Does `git filter-branch` complete successfully? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus Heuristic is an algorithm in a clown suit. It’s less predictable, it’s more fun, and it comes without a 30-day, money-back guarantee. -- Steve McConnell, Code Complete
Description: PGP signature