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] Documenting the SOC tree Repository
Date: Sun, 3 May 2020 01:21:45 +0100
Message-ID: <CAPweEDxy4mm6T-RgGwgiMAgQ7E2NtB4z4-Sh96CXUEuihxAxjw@mail.gmail.com> (raw)
In-Reply-To: <6A20EC57-766F-4711-9233-785F162C1D3B@gatech.edu>
On Sunday, May 3, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:
>
>
> > On May 2, 2020, at 7:24 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
> >
> > i really do not like branches.
>
> OK no branches
appreciated.
> I’d like to move the CSVs to the soc repo, and then do an iframe to the
> git tree raw to display in the wiki.
a simpler proposal is to write a script that commits and copies the files
to the other (ikiwiki) repo.
some instructions can be placed in isatables indicating where the canonical
versions are (in soc).
however this again leaves
> I can wrap it in a little js to get the browser to render the csv as a
> table.
hm hm that makes js a hard dependency where it presently is not.
i wonder if the postcommit hook in ikiwiki could be modified to pretend
that the files are in the same repo. the static html would then be built
still from the same source.
>
> It doesn’t make sense to submodule the entire wiki in the SOC repo just
> for some tables. That’s structurally wrong.
i honestly don't know the best option here. duplication risks getting out
of sync. all ootions have disadvantages
> Moving the CSVs directly into the SOC repo is low priority for me now -
> but, I’m just putting it out there - its something that needs to be
> addressed sooner than later.
the postcommit option i can ask alain if he can have a look.
l.
>
> Yehowshua
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
>
--
---
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
prev parent reply index
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 3:09 Yehowshua
2020-05-02 4:40 ` Luke Kenneth Casson Leighton
2020-05-02 4:42 ` Yehowshua
2020-05-02 20:59 ` Yehowshua
2020-05-02 23:24 ` Luke Kenneth Casson Leighton
2020-05-03 0:08 ` Yehowshua
2020-05-03 0:09 ` Yehowshua
2020-05-03 0:21 ` Luke Kenneth Casson Leighton [this message]
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=CAPweEDxy4mm6T-RgGwgiMAgQ7E2NtB4z4-Sh96CXUEuihxAxjw@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