From: Junsong Li <ljs.darkfish@gmail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Kakadu <kakadu.hafanana@gmail.com>,
John Whitington <john@coherentgraphics.co.uk>,
Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] About recently dead compiler-hacking wiki
Date: Fri, 30 Sep 2016 17:07:21 -0700 [thread overview]
Message-ID: <CA+kGxtOy3tXWea9f50CentDCUbOxPYLW48+YCguS9BMXjFUYGQ@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBE+4TYtqthi8gYcS5hoFXHit2aRWEMvdY4-HuCKOLO8CA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2220 bytes --]
Wow, I think Gabriel's list is more tangible than that wiki.
@Kakadu the wiki is for a local OCaml hacking group, so it may be outdated,
and the listed projects are not agreed by the core team. You need to
discuss with them the viability of the project before the attack!
On Fri, Sep 30, 2016 at 6:48 AM, Gabriel Scherer <gabriel.scherer@gmail.com>
wrote:
> To look for issues tagged junior_job from http://caml.inria.fr/mantis/
> view_all_bug_page.php , first reset your current Mantis filter ("Reset
> filter"), then click the "Tags" link in the filter form, that will open an
> input field where you can write (or select) "junior_job".
>
> The following link also works (built using the "Create Permalink" option
> to get a URL from a filter):
>
> http://caml.inria.fr/mantis/search.php?project_id=1&
> resolution_id[]=10&resolution_id[]=30&sticky_issues=on&
> sortby=last_updated&dir=DESC&hide_status_id=-2&tag_string=junior_job
>
> On Fri, Sep 30, 2016 at 9:33 AM, Kakadu <kakadu.hafanana@gmail.com> wrote:
>
>> John,
>>
>> This search gives me only 3 issues that are not closed. Am I doing
>> the search righ?
>>
>> Kakadu
>>
>> On Fri, Sep 30, 2016 at 4:07 PM, John Whitington
>> <john@coherentgraphics.co.uk> wrote:
>> > Hi,
>> >
>> > Kakadu wrote:
>> >>
>> >> Hey, folks
>> >>
>> >> Compiler hacking is fun. Hacking compiler with a feature that can be
>> >> potentially appreciated is a double fun. But ocamllabs wiki is dead.
>> >> Do we have a list of crazy ideas for compiler on mantis or somewhere
>> >> else to work ourselves or give to undergraduates as a pet project?
>> >
>> >
>> > The ocamllabs wiki used to have a list of good things for beginners. In
>> that
>> > vein, there are a few things marked 'junior_job' here:
>> >
>> > http://caml.inria.fr/mantis/view_all_bug_page.php
>> >
>> > (Use 'junior_job' as the search term)
>> >
>> > John
>> >
>> > --
>> > John Whitington
>> > Director, Coherent Graphics Ltd
>> > http://www.coherentpdf.com/
>> >
>>
>> --
>> Caml-list mailing list. Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
>
>
[-- Attachment #2: Type: text/html, Size: 4278 bytes --]
next prev parent reply other threads:[~2016-10-01 0:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 12:58 Kakadu
2016-09-30 13:07 ` Anil Madhavapeddy
2016-09-30 13:07 ` John Whitington
2016-09-30 13:33 ` Kakadu
2016-09-30 13:48 ` Gabriel Scherer
2016-10-01 0:07 ` Junsong Li [this message]
2016-10-01 5:22 ` Kakadu
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+kGxtOy3tXWea9f50CentDCUbOxPYLW48+YCguS9BMXjFUYGQ@mail.gmail.com \
--to=ljs.darkfish@gmail.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=john@coherentgraphics.co.uk \
--cc=kakadu.hafanana@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