<oriansj>Melg8[m]: I always encourage people to find and report bugs in all the tools used in bootstrapping as they must be robust and reliable. <oriansj>So fuzz M2-Planet to your heart's content. However I must warn you that I have already fuzzed it for more than 24hours straight with AFL without finding anything. So anything you find will be of great interest to me. <oriansj>stikonas: well it probably is possible to incorporate cd support into kaem-optional without adding too many bytes but there is one additional option which might work for live-bootstrap better. <oriansj>I could make a hard-coded stub binary in only a handful of bytes that just cd into a known directory (say /stage0-posix) and then execs kaem-optional-seed with no options. <oriansj>(or a specific .kaem file or with some environment if one wanted) <oriansj>xentrac: yeah stikonas is correct the use of SYS_ioctl is in lib/m2/isatty.c which could possibly be removed if we never wish to run MesCC in interactive mode while bootstrapping. <xentrac>I think interactive use is important <siraben>oriansj: ping on whether to rebase/merge blynn compiler <siraben>The module stuff is quite valuable to have for future progress ***Server sets mode: +cnt
***Server sets mode: +cnt
<oriansj>siraben: rebase might be cleaner code-wise and that will be fine. <oriansj>Melg8[m]: thank you for the bug reports. I think I have working commits that fix the first 2. ***Server sets mode: +cnt
<Hagfish>looks like JIRA needs to lower their prices <Hagfish>i don't know whether this new feature lets you manage tasks across multiple different repos <Hagfish>i guess you can always make an issue include a link to the other repo <Hagfish>if people here thought that a more structured collaboration process would be worth the overhead in terms of time spent, it's something to consider