--- Log opened Tue Dec 19 00:00:05 2017 | ||
shorne_ | Marex: I dont, its just a suggestion now, have you seen something like that before? | 00:52 |
---|---|---|
-!- mripard_ is now known as mripard | 04:27 | |
Marex | shorne_: maybe you can bend travisci , they have some tier for FOSS projects | 06:24 |
Marex | shorne_: we use that to build-test uboot | 06:24 |
shorne_ | Marex: we use travisci as well, just for builds | 07:16 |
shorne_ | I have some other things on my todo list, I want to look into this, wallento any thoughts on nightly merge vs rebase? | 07:17 |
wallento | shorne: I agree on the idea | 07:17 |
wallento | but I am not sure if the rebase shouldn't be a manual step | 07:17 |
wallento | Marex, shorne: we will use LibreCores CI for that I suppose | 07:18 |
Marex | the rebase can run into conflicts quickly indeed | 07:48 |
Marex | shorne_: wallento but I'm just a newcomer running my mouth at random, so feel free to ignore me | 07:49 |
shorne_ | wallento: yeah, we can get conflicts, another idea I have is | 09:11 |
shorne_ | 1. maintain feature branches (for any features that need to go updataem, like linux-next) | 09:12 |
shorne_ | 2. merge each feature branch onto upstream on a daily bases as openrisc-next. | 09:12 |
shorne_ | that works well for linux, its a bit task since ther are ~200 feature branch repos to pull | 09:13 |
shorne_ | but for us, we will have less than a handful of feature branches | 09:13 |
shorne_ | maybe just or1k-gcc at the moment | 09:13 |
shorne_ | (FYI) I will be testing this out on or1k-gcc to track 7.x, 8.x ... going forward | 09:14 |
nooga | hi | 15:59 |
nooga | I'm porting s-macke's jor1k to JVM for giggles and I got my CPU emu to compile but I don't know how to even start testing it | 16:02 |
nooga | I've seen some tests on openrisc github but I looked through the sim configs there and I fear that running these tests would be more work than writing the emu | 16:03 |
ZipCPU | nooga: Most of the OpenRISC types work in non-US time-zones. You might wish to be patient for an answer. Sometimes responses take nearly 24-hrs or so. | 17:12 |
nooga | thanks ZipCPU | 17:13 |
nooga | I'm in europe myself ;) | 17:13 |
--- Log closed Wed Dec 20 00:00:07 2017 |
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!