Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • This seems like it would work, but ... isn't there any way to just use Git (with no shell scripts) and make the process automated via a "git filter-branch --commit-filter"? Commented Jan 4, 2011 at 22:26
  • 1
    The help for --commit-filter specifically mentions that skip_commit leaves out the commit but not the changes and says to use git-rebase instead. filter-branch considers your revisions as a sequence of states and allows you to permute each commit, but the changes to not propagate to the children. rebase considers your revisions as a stack of patches and any modification midstream does propagate to future revisions. But that can cause failures which is why it can't be fully automatic. Commented Jan 4, 2011 at 22:35