On Fri, Aug 9, 2013 at 6:32 AM, Johannes Sixt <j.s...@viscovery.net> wrote:
> Am 8/9/2013 12:03, schrieb shawn wilson:
>> The question still stands though - why is that unassociated commit left 
>> there?
> Because your command did not remove it. filter-branch does not know that
> it is "unassociated" when you ask it to follow all commits beginning at
> HEAD. But when you say 'HEAD -- webban.pl', you ask it to follow only
> commits that touch webban.pl, which automatically skips that commit.

I can go with that. However, I don't think that's the end of the story either:
 % du -sh .
192M    .

Something has been left behind. What? Or how do I figure that out and remove it?
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to