On Tue, May 6, 2025 at 6:26 AM Dan McDonald <
[email protected]> wrote:

> I'm still in the spin-down process of a set of Ms&As so I'm not sure under
> whose name I'd register my company, or if they'd let me contribute as an
> individual.
>

Well, you'll have to figure that out obviously, and it's unrelated to how
you submit your patches: just putting them up for download somewhere
doesn't avoid the official authorship question.
At any rate we'll need a corporate or personal CLA submission.


>
> Patches generally land on the main branch. Backmerges to old branches
> (such as 13.6) would need special justification.
>
>
> Node took the illumos-only patch for their import of 13.6, which was kind
> and supportive of them.  I'm not expecting V8 to accept backports. I hope
> to have illumos changes upstream before the NEXT time Node updates their V8
> revision.
>

That's fine. Your previous message sounded like "depending on a modern V8"
was a limitation/concern, to which I wanted to reply that it's not, on the
contrary.


>
>
> Note that illumos is officially unsupported by the core V8 team, i.e. it's
> only supported by interested community members such as yourself.
>
>
> I noticed this in BUILD.gn:
>
>       `  # TODO(infra): Add support for qnx, freebsd, openbsd, netbsd,
> and solaris.`
>
> Do you support Oracle Solaris?  We aren't THAT much different from our
> closed-source peer descendant.
>

No, none of these are officially supported. That comment is ~11 years old,
which gives some indication of the priority of (and demand for) doing
anything for these OSs. We could probably just drop it to reflect reality.

-- 
-- 
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- 
You received this message because you are subscribed to the Google Groups 
"v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/v8-dev/CAKSzg3Rf9V6UWENwWYUeKedz9_A%2Ba4ikuo%2BD9xnkZaagTOVjRw%40mail.gmail.com.

Reply via email to