feremondo.blogg.se - How to uninstall make visuals great again

Notice that the new “Careless” commit adds only other.html and that the “Remove DVD-rip” commit is no longer on the master branch. | * f772d66 (refs/original/refs/heads/master) Login page Your repository, like the sample above, may have only one ref (master), but I included this option for full generality.Īfter some churning, the history is now: $ git lola -name-status

-all following - is shorthand for all refs.

- specifies the end of options to git filter-branch.

Your repository, like the sample above, may not have any tags, but I included this option for full generality. A filter of cat is the identity operation.

-tag-name-filter describes how to rewrite tag names.

The command git rm -cached -f -ignore-unmatch oops.iso deletes the DVD-rip when it is present and does not fail otherwise. You want to remove oops.iso wherever it is found, but it isn’t present in all commits.

-index-filter is the main event and runs against the index at each step in the history.

If you are running on a modern Linux distribution, specifying a tree in /dev/shm will result in faster execution.

-d names a temporary directory that does not yet exist to use for building the filtered history.

In the typical case, this option produces a cleaner history.

-prune-empty removes commits that become empty ( i.e., do not change the tree) as a result of the filter operation.index-filter "git rm -cached -f -ignore-unmatch oops.iso" \ Using the technique described in the aforementioned blog post, the command to execute is: git filter-branch -prune-empty -d /dev/shm/scratch \ In the “Careless” commit (whose SHA1 object name is ce36c98) the file oops.iso is the DVD-rip added by accident and removed in the next commit, cb14efd.

(See the addendum at the end of this answer for details.) The -name-status switch to git log shows tree modifications associated with each commit. Note that git lola is a non-standard but highly useful alias. Say your git history is: $ git lola -name-status I had a similar problem with bulky binary test data from a Subversion import and wrote about removing data from a git repository. You have at least two options: git filter-branch and an interactive rebase, both explained below. See “Recovering From Upstream Rebase” in the git rebase documentation for the necessary steps after repairing your history.

What you want to do is highly disruptive if you have published history to other developers.