Skip to content

Conversation

@Machine-Maker
Copy link
Member

After changing branches, applying patches, changing to other branches, this seems to prevent the frequent message that instructs users to run git prune and then delete .git/gc.log.

Can add if needed, the deletion of the .git/gc.log file, as that's what actually stops the warning message from being shown

@Machine-Maker Machine-Maker changed the title Run git gc after applying patches Run git prune after applying patches Jan 11, 2022
@electronicboy
Copy link
Member

This is a weird area where pruning much of the time is generally somewhat of an idea given how we rip the tree apart so violently, but, those loose objects can be used during a 3 way to aid in merging automagically

@Machine-Maker
Copy link
Member Author

Yeah, I don't know enough about how git works to know what exactly causes the issue I'm trying to fix here, but DenWav said PRs are open for it, so I took a stab at it. I haven't noticed anything bad so far, but just might not have done the one thing that this breaks, or hampers.

@electronicboy electronicboy deleted the branch PaperMC:main December 13, 2024 21:02
@jpenilla
Copy link
Member

Reopening, not sure if this is relevant anymore (probably not?)

@jpenilla jpenilla reopened this Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants