git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Removing things from a repo that shouldn't be there

From
Jon Smirl <jonsmirl@gmail.com>
Date
Feb 10, 2008, 17:15 UTC
Message-ID
<9e4733910802100915t56d0f63fh90c303b35f6af921@mail.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
Next: Johannes Schindelin
Message 1 of 2 in “Removing things from a repo that shouldn't be there”
  1. Jon SmirlFeb 10, 2008
  2. Johannes SchindelinFeb 10, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.