Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mods are out of date #3

Open
HybridDog opened this issue Nov 1, 2017 · 2 comments
Open

Mods are out of date #3

HybridDog opened this issue Nov 1, 2017 · 2 comments

Comments

@HybridDog
Copy link

The mesecons mod's version is from 2014: https://github.com/HarpNetStudios/moontest/commits/master/mods/mesecons

git subtree can be used to cleanly keep mods up to date and keep moontest-related changes

@yellowberryHN
Copy link
Member

Hmm, ok... I guess you are right, could you please elaborate on exactly how I could do that?

@HybridDog
Copy link
Author

remove mesecons/, git add and commit, then add the mod back with
git subtree add --prefix=mods/mesecons/ https://github.com/minetest-mods/mesecons master --squash
https://github.com/HybridDog/moontest/tree/subtree_r
If I understand the man page correctly, git subtree split --onto=<commit_id> can somehow be used to avoid removing and readding mesecons but I didn't figure out how it works.
In moontest there's the mesecons_compatibility removal commit. But the new mesecons doesn't seem to have this folder.

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

No branches or pull requests

2 participants