Removing things from a repo that shouldn't be there

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Git Mailing List <git@...>
Date: Sunday, February 10, 2008 - 1:15 pm

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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Removing things from a repo that shouldn't be there, Jon Smirl, (Sun Feb 10, 1:15 pm)
Re: Removing things from a repo that shouldn't be there, Johannes Schindelin, (Sun Feb 10, 1:38 pm)