From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 291] HDL Workflow and Coriolis2 chroot automated setup scripts
Date: Wed, 13 May 2020 02:00:18 +0000
Message-ID: <bug-291-13-wq8QofeZlZ@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=291
--- Comment #7 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #6)
> ok so there's nothing in there which says "picking a hard-coded git tag
> number"
> so i suspect that it's as simple as jean-paul made a commit recently which
> broke something.
Ah, I'm realizing now that I really should have been using a hard-coded git tag
number. Can you share your known-working git tag number for coriolis2 so I can
continue working on the script tomorrow?
--
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
next prev parent reply index
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 21:42 [libre-riscv-dev] [Bug 291] New: " bugzilla-daemon
2020-04-21 21:46 ` [libre-riscv-dev] [Bug 291] " bugzilla-daemon
2020-05-12 19:41 ` bugzilla-daemon
2020-05-13 0:09 ` bugzilla-daemon
2020-05-13 0:15 ` bugzilla-daemon
2020-05-13 0:16 ` bugzilla-daemon
2020-05-13 1:19 ` bugzilla-daemon
2020-05-13 2:00 ` bugzilla-daemon [this message]
2020-05-13 9:19 ` bugzilla-daemon
2020-05-13 17:58 ` bugzilla-daemon
2020-05-15 21:18 ` bugzilla-daemon
2020-05-18 20:26 ` bugzilla-daemon
2020-05-18 20:30 ` bugzilla-daemon
2020-05-18 20:37 ` bugzilla-daemon
2020-05-18 21:02 ` bugzilla-daemon
2020-05-18 22:15 ` bugzilla-daemon
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-291-13-wq8QofeZlZ@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.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