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

please consider a short note about where patches are found and process to apply #643

Open
kencu opened this issue Apr 25, 2021 · 1 comment

Comments

@kencu
Copy link
Contributor

kencu commented Apr 25, 2021

I have not really understood exactly where the new changes come from upstream, and how to screen them to apply them to this codebase.

Perhaps you might have a moment to add a note about how you do that to the readme?

For building, I have had a working MacPorts portfile for some time. I will try to get that up into the MP repo so it can be built there.

Thanks for everything!

@classilla
Copy link
Owner

classilla commented Apr 25, 2021

Sure, though any patches I land will still go to this tree.

They come from the current ESR, whatever that is. You can peruse committed diffs, even if you can't see the underlying issue reports until they are "declassified," from https://hg.mozilla.org/releases/mozilla-esr78 (adjust for version).

The scripts ./104fx_upcerts.sh and ./104fx_uptzdata.sh automate the processes of updating certificates, eTLDs, roots, HSTS lists, cryptominer blocks and internationalization timezone data.

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