From: Philip Oakley <philipoakley@iee.org>
Date: Fri, 20 Jan 2017 22:28:15 GMT
Subject: Idea: Add a filter option to 'git rebase'
Message-ID: <8AED6D90D2B64AE3A63C6195CA983FE8@PhilipOakley>

A recent question on stackoverflow 
http://stackoverflow.com/questions/41753252/drop-commits-by-commit-message-in-git-rebase 
sought to remove automatically commits that could be identified by relevant 
words in the commit message.

I had thought that the ubiquitous `git filter-branch` should be able to do 
this sort of thing. I was wrong. (It was pointed out to me that...) The man 
page notes that removing a commit via filter-branch does not remove the 
changes from following commits and directs readers to using `git rebase(1)`.

However the rebase command does not have any filter option to allow the 
automatic population of its TODO list with the appropriate 
pick/edit/drop/etc. values.

It does feel as if a --filter style option would be a useful addition to 
rebase to complement the filter-branch options once the current conversion 
from script to code is complete.

Is this something that should be put in the 'worth considering' pile?

--
Philip