mirror of
https://github.com/nodejs/node.git
synced 2025-05-19 00:19:36 +00:00
8a43a3d761
Pick up the latest branch head for V8 4.7:
be169f8df0
Full change history for the 4.7 branch:
https://chromium.googlesource.com/v8/v8.git/+log/branch-heads/4.7
V8 blog post about what is new on V8 4.7:
http://v8project.blogspot.de/2015/10/v8-release-47.html
PR-URL: https://github.com/nodejs/node/pull/4106
Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: targos - Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: rvagg - Rod Vagg <rod@vagg.org>
24 lines
869 B
Markdown
24 lines
869 B
Markdown
# General
|
|
This article describes how ports should be handled.
|
|
|
|
# MIPS
|
|
## Straight-forward MIPS ports
|
|
1. Do them yourself.
|
|
|
|
## More complicated MIPS ports
|
|
1. CC the MIPS team in the CL. Use the mailing list v8-mips-ports.at.googlegroups.com for that purpose.
|
|
1. The MIPS team will provide you with a patch which you need to merge into your CL.
|
|
1. Then land the CL.
|
|
|
|
# PPC (not officially supported)
|
|
1. Contact/CC the PPC team in the CL if needed. Use the mailing list v8-ppc-ports.at.googlegroups.com for that purpose.
|
|
|
|
# x87 (not officially supported)
|
|
1. Contact/CC the x87 team in the CL if needed. Use the mailing list v8-x87-ports.at.googlegroups.com for that purpose.
|
|
|
|
# ARM
|
|
## Straight-forward ARM ports
|
|
1. Do them yourself.
|
|
|
|
## When you are lost
|
|
1. CC the ARM team in the CL. Use the mailing list v8-arm-ports.at.googlegroups.com for that purpose. |