{"thread":{"id":"12010","subject":"Removing things from a repo that shouldn't be there","startedAt":"2008-02-10T17:15:43Z","lastAt":"2008-02-10T17:38:20Z","messageCount":2,"participants":["Jon Smirl","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"68235","messageId":"9e4733910802100915t56d0f63fh90c303b35f6af921@mail.gmail.com","threadId":"12010","inReplyTo":null,"subject":"Removing things from a repo that shouldn't be there","fromName":"Jon Smirl","fromEmail":"jonsmirl@gmail.com","sentAt":"2008-02-10T17:15:43Z","receivedAt":"2008-02-10T17:15:43Z","isPatch":false,"sender":{"key":"jonsmirl@gmail.com","avatar":"https://gravatar.com/avatar/cff3bf5bfdfa6708b905712ff91f0f9b8aaca161659f38c02b787920d5d28b7e?d=mp&s=160"},"body":"In the lazy clone thread there is mention of a large, generated file\nbeing checked into the tree. Let's say we have a tree like this and it\nis ok to delete the generated file since it didn't really need to be\nchecked in. Is there a procedure to chase down all the revisions,\ndelete them, and then regenerate the commits to reflect the deletion?\nI don't need this tool, I'm just wondering if there is a reasonable\nsolution to the problem.\n\n-- \nJon Smirl\njonsmirl@gmail.com\n"},{"id":"68237","messageId":"alpine.LSU.1.00.0802101738120.11591@racer.site","threadId":"12010","inReplyTo":"9e4733910802100915t56d0f63fh90c303b35f6af921@mail.gmail.com","subject":"Re: Removing things from a repo that shouldn't be there","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-02-10T17:38:20Z","receivedAt":"2008-02-10T17:38:20Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sun, 10 Feb 2008, Jon Smirl wrote:\n\n> In the lazy clone thread there is mention of a large, generated file \n> being checked into the tree. Let's say we have a tree like this and it \n> is ok to delete the generated file since it didn't really need to be \n> checked in. Is there a procedure to chase down all the revisions, delete \n> them, and then regenerate the commits to reflect the deletion? I don't \n> need this tool, I'm just wondering if there is a reasonable solution to \n> the problem.\n\nfilter-branch.\n\nCiao,\nDscho\n"}]}