# Removing things from a repo that shouldn't be there 2 messages from 2008-02-10 to 2008-02-10. Participants: Jon Smirl, Johannes Schindelin. Thread: https://gitlist.dev/t/12010 ## Jon Smirl, 2008-02-10 17:15 Subject: Removing things from a repo that shouldn't be there Message-ID: <9e4733910802100915t56d0f63fh90c303b35f6af921@mail.gmail.com> URL: https://gitlist.dev/e/9e4733910802100915t56d0f63fh90c303b35f6af921%40mail.gmail.com ``` In the lazy clone thread there is mention of a large, generated file being checked into the tree. Let's say we have a tree like this and it is ok to delete the generated file since it didn't really need to be checked in. Is there a procedure to chase down all the revisions, delete them, and then regenerate the commits to reflect the deletion? I don't need this tool, I'm just wondering if there is a reasonable solution to the problem. -- Jon Smirl jonsmirl@gmail.com ``` ## Johannes Schindelin, 2008-02-10 17:38 Subject: Re: Removing things from a repo that shouldn't be there Message-ID: URL: https://gitlist.dev/e/alpine.LSU.1.00.0802101738120.11591%40racer.site In-Reply-To: <9e4733910802100915t56d0f63fh90c303b35f6af921@mail.gmail.com> ``` Hi, On Sun, 10 Feb 2008, Jon Smirl wrote: > In the lazy clone thread there is mention of a large, generated file > being checked into the tree. Let's say we have a tree like this and it > is ok to delete the generated file since it didn't really need to be > checked in. Is there a procedure to chase down all the revisions, delete > them, and then regenerate the commits to reflect the deletion? I don't > need this tool, I'm just wondering if there is a reasonable solution to > the problem. filter-branch. Ciao, Dscho ```