From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] GitLab CI Archiver
Date: Wed, 8 Apr 2020 17:15:40 +0100
Message-ID: <CAPweEDx=pYNXvapRZyxySeL2VeC_cGQC44X=ye0W-kUcqJMzgg@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD5CVz8x3rEkt8pu=eVh4mGQV7QZ5AfrmhmapR3EnUfZww@mail.gmail.com>
On Wed, Apr 8, 2020 at 4:42 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> Sorry, I ended up writing a Rust program that does at least part of
> what we need (I thought it might take an hour or two -- it took 10):
we need to be careful about that: sysadmin tasks are typically done in
bash, using awk, sed, grep, curl and others.
alain will definitely be unable to work on rust programs: he'll be
able to install and use them but it will take him potentially 3-8
months full-time (doing nothing else) to get to the point where he
could _modify_ - take over - anything written in rust, and maintain
it.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 14:37 [libre-riscv-dev] Broken build notification from debian salsa Jacob Lifshay
2020-04-07 15:00 ` Luke Kenneth Casson Leighton
2020-04-07 15:13 ` Jacob Lifshay
2020-04-07 15:47 ` Luke Kenneth Casson Leighton
2020-04-07 15:52 ` Luke Kenneth Casson Leighton
2020-04-07 16:00 ` Jacob Lifshay
2020-04-07 16:41 ` Jacob Lifshay
2020-04-07 16:52 ` Luke Kenneth Casson Leighton
2020-04-08 15:42 ` [libre-riscv-dev] GitLab CI Archiver Jacob Lifshay
2020-04-08 16:15 ` Luke Kenneth Casson Leighton [this message]
2020-04-09 20:25 ` Jacob Lifshay
2020-04-07 15:03 ` [libre-riscv-dev] Broken build notification from debian salsa Immanuel, Yehowshua U
2020-04-07 15:10 ` Luke Kenneth Casson Leighton
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='CAPweEDx=pYNXvapRZyxySeL2VeC_cGQC44X=ye0W-kUcqJMzgg@mail.gmail.com' \
--to=lkcl@lkcl.net \
--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