{"json_modified": "2016-03-28T07:58:03.749382", "uuid": "a3384170-f750-4cc8-8821-cb7b2f2aaa28", "title": "How to Write and Land Nanojit Patches", "url": "/en-US/docs/Archive/Mozilla/Nanojit_merging", "tags": ["Obsolete"], "translations": [], "modified": "2014-03-21T14:23:58", "label": "How to Write and Land Nanojit Patches", "localization_tags": [], "locale": "en-US", "id": 5024, "last_edit": "2014-02-07T13:50:15", "summary": "Adobe and Mozilla share a copy of Nanojit. This means that landing nanojit patches is a bit complicated, but experience has taught us that this is <strong>much</strong> better than having separate versions of nanojit.", "sections": [{"id": "Resources", "title": "Resources"}, {"id": "Procedure", "title": "Procedure"}, {"id": "Scenario_0_a_common_prefix_for_all_scenarios", "title": "Scenario 0: a common prefix for all scenarios"}, {"id": "Scenario_1_creating_an_internal_(ie._Nanojit-only)_patch", "title": "Scenario 1: creating an internal (ie. Nanojit-only) patch"}, {"id": "Scenario_2_creating_an_external_patch", "title": "Scenario 2: creating an external patch"}, {"id": "Scenario_3_doing_a_periodic_NJ-to-TMTR_update", "title": "Scenario 3: doing a periodic NJ-to-TM/TR update"}, {"id": "Scenario_4_if_you_break_something", "title": "Scenario 4: if you break something"}], "slug": "Archive/Mozilla/Nanojit_merging", "review_tags": []}