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] Merging Repositories and Auto-Generating Static Documentation
Date: Mon, 4 May 2020 10:23:30 +0100
Message-ID: <CAPweEDzSRkSFHBVnwyLnjua=Uwz9n5rQ4pCbiy-yw-3CCX7zPA@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDwQgu0r+S7U0a_0zK-qaNXCeH_Jek66Gn4yd7XAT=9gTA@mail.gmail.com>
yehowshua: i understand the desire to reorganise because it gives you a
reason to go over everything, and thus crystallises the code in your mind
as working knowledge.
i really appreciate that you made the decision, several months ago, to help
with funding instead of coding as it is a critical step in the process.
however as we have only 15 weeks is the worst possie time to carry out
major reorganising.
it is a major distraction even to discuss this. i estimate it will be about
a WEEK to complete including rewriting all tutorials, automated scripts,
all of which critically depend on the repo structure.
alain is currently focussing on designing the ISA ready to present to
OpenPOWER. he cannot afford the time to be distracted. i had to stop
myself from asking him to do something else, even 30 minutes ago.
the critical priority need right now is *coding* in order to meet the
deadline.
can we please, everyone, focus on coding and on completing the tasks as
fast as possible.
l.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
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: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 2:13 Yehowshua
2020-05-04 8:33 ` Luke Kenneth Casson Leighton
2020-05-04 9:23 ` Luke Kenneth Casson Leighton [this message]
2020-05-04 12:59 ` Luke Kenneth Casson Leighton
2020-05-04 13:10 ` Yehowshua
2020-05-04 13:14 ` 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='CAPweEDzSRkSFHBVnwyLnjua=Uwz9n5rQ4pCbiy-yw-3CCX7zPA@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