Am 8/8/2013 23:11, schrieb Phil Hord: > On Wed, Aug 7, 2013 at 5:07 PM, shawn wilson <ag4ve.us@xxxxxxxxx> wrote: >> On Wed, Aug 7, 2013 at 6:43 AM, Johannes Sixt <j.sixt@xxxxxxxxxxxxx> wrote: >>> Am 8/7/2013 8:24, schrieb shawn wilson:> ... create a repo for one of >>>> these scripts and I'd like to keep the commit history. >>>> >>>> Ok, so: >>>> % find -type f ! -iname "webban.pl" | while read f; do git >>>> filter-branch -f --index-filter "git rm --cached --ignore-unmatch $f" >>>> HEAD ; done >>>> >>>> Which basically did it. But, I've got this one commit that seems to be >>>> orphaned - it doesn't change any files. >>> >>> Try this: >>> >>> git filter-branch HEAD -- webban.pl >>> >> >> % git filter-branch HEAD -- webban.pl >> Cannot create a new backup. >> A previous backup already exists in refs/original/ >> Force overwriting the backup with -f >> % git filter-branch -f HEAD -- webban.pl >> Rewrite 1e04b18c256c996312f167be808733bcc755f1e3 (9/9) >> WARNING: Ref 'refs/heads/master' is unchanged > > I think you can ignore the warning. Maybe you want to create a new > branch which only has this file in it now. > > $ git checkout -b webban I'm not sure. On second thought, my suggested command is not sufficient. It does remove the empty commits, but it does not remove the other files. So, Shawn's original filter-branch invocations are still needed. -- Hannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html