2 ms·
Maintain your own forks of the libraries you need. Commit your changes there, and also submit upstream. Pull upstream changes back to your fork when you are rea
by wereHamster 13y ago
Maintain your own forks of the libraries you need. Commit your changes there, and also submit upstream. Pull upstream changes back to your fork when you are ready. You have this problem with any language or tool that uses github directly as the registry.
- npsimons 13y agoMaintain your own forks of the libraries you need. Exactly this. This is just one reason I really like to "git clone --mirror" onto my server, then clone from that, and work from there.
- beagle3 13y agoWhat's the benefit of that, as opposed to cloning upstream and working on that clone? How does the intermediate mirror help?
- npsimons 13y agoI've run into the problem (with some Emacs add-ons in particular), of changing something on one machine, only to miss that change in another. So, if I've got my own "central" repo, I can push changes to that and pull them down to other machines. Since I site the repos on a server I have online already, it is also trivially easy to make it publicly "pullable" for others if need be.