Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: bugzilla-daemon@libre-riscv.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 178] first coriolis2 tutorial, workflow and "test project" page
Date: Wed, 18 Mar 2020 14:38:01 +0000
Message-ID: <bug-178-13-xea8svHLfG@http.bugs.libre-riscv.org/> (raw)
In-Reply-To: <bug-178-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=178

--- Comment #212 from Jock Tanner <tanner.of.kha@gmail.com> ---
I don't know if I'm expected to react somehow, but for me it's fine. I only
think if anyone could enlighten me about the due procedures.

(In reply to Luke Kenneth Casson Leighton from comment #210)
> for this one, i'm going to suggest:
> 
> * EUR 250 to jock for the (crucial) questions and for helping get to buster 
> * EUR 200 to tobias for the early checking of the tutorial
> * EUR 700 to be donated to LIP6.fr for the huge amount of bugfixing by JP
> * EUR 150 to Staf for his insights
> * EUR 1200 to me for the persistent head-banging against brick walls
> 
> Cole, as long as you are in Europe, you helped find some early bugs in the
> tutorial page, and made some useful edits, however if you are outside of
> Europe, most of what NLNet would transfer to you would go in banking fees. 
> we can if you like work something out.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  parent reply index

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-178-13@http.bugs.libre-riscv.org/>
2020-03-11 12:35 ` bugzilla-daemon
2020-03-11 12:45 ` bugzilla-daemon
2020-03-11 12:59 ` bugzilla-daemon
2020-03-11 14:51 ` bugzilla-daemon
2020-03-11 15:35 ` bugzilla-daemon
2020-03-12 11:23 ` bugzilla-daemon
2020-03-12 11:48 ` bugzilla-daemon
2020-03-12 16:15 ` bugzilla-daemon
2020-03-12 17:14 ` bugzilla-daemon
2020-03-12 17:25 ` bugzilla-daemon
2020-03-13 16:21   ` Cole Poirier
2020-03-15 19:57 ` bugzilla-daemon
2020-03-18 14:38 ` bugzilla-daemon [this message]
2020-03-18 15:18 ` bugzilla-daemon
2020-03-18 22:47 ` bugzilla-daemon
2020-03-18 23:41 ` bugzilla-daemon
     [not found] <bug-178-13@https.bugs.libre-soc.org/>
2020-04-21 21:00 ` bugzilla-daemon
2020-04-21 21:09 ` bugzilla-daemon
2020-04-21 21:15 ` bugzilla-daemon
2020-04-21 21:28 ` bugzilla-daemon
2020-04-21 21:30   ` Luke Kenneth Casson Leighton
2020-04-21 21:35     ` Cole Poirier

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=bug-178-13-xea8svHLfG@http.bugs.libre-riscv.org/ \
    --to=bugzilla-daemon@libre-riscv.org \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    /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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git