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.

Sign up for GitHub

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

Jump to bottom

doc: recommend git-node-v8 #43934

Merged
merged 4 commits into from
Jul 25, 2022
Merged

doc: recommend git-node-v8 #43934

merged 4 commits into from
Jul 25, 2022

Commits on Jul 21, 2022

  1. doc: recommend git-node-v8 

    Per the comments in nodejs#43924, almost everyone uses `git-node-v8`. I
included example steps for using `git-node-v8`.

I ran through both of these instructions on a clean Linux machine (I had
to fudge the patch SHA of course) and they seemed to work.

Refs: nodejs#43924
    @kvakil
    kvakil committed Jul 21, 2022
    Configuration menu
    Copy the full SHA
    85c517f View commit details
    Browse the repository at this point in the history

  2. suggestions

    @kvakil
    kvakil committed Jul 21, 2022
    Configuration menu
    Copy the full SHA
    b88ea17 View commit details
    Browse the repository at this point in the history

  3. oops; forgot format

    @kvakil
    kvakil committed Jul 21, 2022
    Configuration menu
    Copy the full SHA
    5b61c66 View commit details
    Browse the repository at this point in the history

Commits on Jul 24, 2022

  1. Update doc/contributing/maintaining-V8.md 

    Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
    @kvakil @aduh95
    kvakil and aduh95 authored Jul 24, 2022
    Configuration menu
    Copy the full SHA
    ec65e9e View commit details
    Browse the repository at this point in the history