From: Junsong Li <ljs.darkfish@gmail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Yotam Barnoy <yotambarnoy@gmail.com>,
Goswin von Brederlow <goswin-v-b@web.de>,
Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Flambda/compiler walkthrough + modularity
Date: Tue, 15 Mar 2016 19:12:25 -0700 [thread overview]
Message-ID: <CA+kGxtNkXyAV5LxPDceh7j8KVU5qeX0+QX=vtQ9NjOwTe1Cg_g@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBG-Ya=YXOx3wWH3Oy31060S1pa5HHVXb+S7UyPaNJpUkg@mail.gmail.com>
> Some regions of the codebase have a well-defined maintainer (typing ->
> Jacques Garrigue, pattern-matching -> Luc Maranget, backend -> Xavier Leroy,
> garbage collector -> Damien Doligez), and some people are experts on more
> local or cross-cutting aspects. As far as I know, there is no formal
> ownership structure, but people triaging bugs or change proposals will
> usually know who to ask before making decisions. You don't need to know in
> advance who would be the best reviewer to send a patch.
Oh, Thank you. It is good to know.
> Yes, and this is encouraged. More generally, people should feel free to look
> at the bugreports and try to propose a fix (whether they "know well" the
> affected part of the codebase or not), and to look at the proposed patches
> and review them -- which means commenting on everything that feel strange or
> that you do not understand in the patch.
Thanks.
next prev parent reply other threads:[~2016-03-16 2:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 17:04 Yotam Barnoy
2016-03-14 7:27 ` Mark Shinwell
2016-03-14 10:36 ` Goswin von Brederlow
2016-03-14 12:30 ` Gabriel Scherer
2016-03-14 13:51 ` Yotam Barnoy
2016-03-14 20:31 ` Hendrik Boom
2016-03-14 21:00 ` Yotam Barnoy
2016-03-14 21:05 ` Junsong Li
2016-03-15 1:02 ` Gabriel Scherer
2016-03-16 2:12 ` Junsong Li [this message]
2016-03-18 15:15 ` [Caml-list] <DKIM> " Pierre Chambart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+kGxtNkXyAV5LxPDceh7j8KVU5qeX0+QX=vtQ9NjOwTe1Cg_g@mail.gmail.com' \
--to=ljs.darkfish@gmail.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=goswin-v-b@web.de \
--cc=yotambarnoy@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).