A commit brought in 6,000 or so files. Git still keeps track of these files in case we ever want to revert to that commit. This severely increases the amount of time it takes to clone this repo. Is there a way to make git forget about that commit? Maybe a way to reset to the commit before and manually bring in the recent changes?
owen2
commented
13 years ago
A commit brought in 6,000 or so files. Git still keeps track of these files in case we ever want to revert to that commit. This severely increases the amount of time it takes to clone this repo. Is there a way to make git forget about that commit? Maybe a way to reset to the commit before and manually bring in the recent changes?