Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Cole Poirier <colepoirier@gmail.com>
To: "libre-riscv-dev@lists.libre-riscv.org"
	<libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] Git repository access
Date: Tue, 24 Mar 2020 11:56:06 -0700
Message-ID: <09EAF495-B495-41A4-9BE3-D840DA912D8C@getmailspring.com> (raw)

Hi Luke,

I'm currently working on getting the gitlab test runner set up on
Jacob's build server. While doing this I've been trying to follow
(install?) the HDL workflow, and I think I've reached a point where I
need read access to the git repo. Specifically I'm trying to complete
6.5 Softfloat and sfpy.

###
git clone --recursive https://github.com/billzorn/sfpy.git
cd sfpy
cd SoftPosit
git apply ../softposit_sfpy_build.patch

-> I believe for this I will need ieee754fpu.git/master/SoftPosit.patch
git apply /path/to/ieee754fpu/SoftPosit.patch

cd ../berkely-softfloat-3
# Note: Do not apply the patch included in sfpy for berkely-softfloat, 
# it contains the same changes as this one

-> I believe for this I will need ieee754fpu.git/master/berkeley-softfloat.patch
git apply /path/to/ieee754fpu/berkeley-softfloat.patch
###

If I can access these files without needing permission, or if there is
another way I should go about this, please let me know. I believe you
already have my ssh pub key, but if you need me to send it again that's
no problem.

Cole


_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

             reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 18:56 Cole Poirier [this message]
2020-03-24 20:11 ` Luke Kenneth Casson Leighton
2020-03-24 20:25   ` Cole Poirier
2020-03-24 22:33     ` 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=09EAF495-B495-41A4-9BE3-D840DA912D8C@getmailspring.com \
    --to=colepoirier@gmail.com \
    --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