Skip to content

Conversation

@HO-COOH
Copy link

@HO-COOH HO-COOH commented Mar 28, 2023

No description provided.

@Squall-Leonhart
Copy link

Squall-Leonhart commented Jun 11, 2023

The latest changes in the delayload branch handle versioning differently to master.

@God-damnit-all
Copy link

God-damnit-all commented Sep 4, 2023

The latest changes in the delayload branch handle versioning differently to master.

There's no reason not to merge this PR anyway, though. Even if it becomes obsolete, it's an improvement to the code that might be useful for someone that doesn't want to use the delayload branch's approach for whatever reason.

Perhaps after merging this, the current primary branch could become the legacy branch, and the delayload branch could become the new primary.

@God-damnit-all
Copy link

@ysc3839 I recommend merging this, then making your current main branch the legacy branch, and the delayload branch the new main branch.

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