On 28/06/2021 02.38, BALATON Zoltan wrote:
On Sun, 27 Jun 2021, Richard Zak wrote:
Hopefully last questions:
[...]
2) Is it acceptable to have a patch for the configure script, or is that
generated? I found some Haiku-related issues there
The configure script is not generated, it's just a sh
On Sun, 27 Jun 2021, Richard Zak wrote:
Hopefully last questions:
1) What's the format for the subject line for patches? I'm seeing things
like "[PATCH 2/4]" or "[PATCH v2 00/10]" what do those numbers mean in this
context? I didn't see anything about this mentioned in the SubmitAPatch
wiki.
T
Hopefully last questions:
1) What's the format for the subject line for patches? I'm seeing things
like "[PATCH 2/4]" or "[PATCH v2 00/10]" what do those numbers mean in this
context? I didn't see anything about this mentioned in the SubmitAPatch
wiki.
2) Is it acceptable to have a patch for the c
On Fri, Jun 25, 2021 at 8:45 PM Richard Zak wrote:
> Hello and thanks for the detailed response! I wasn't aware that a Linux
> host could compile for Haiku as a target, that's interesting.
>
> Seems like the big tasks are:
> 1) Haiku VM for continuous integration. Is this hosted in Amazon or othe
Hello and thanks for the detailed response! I wasn't aware that a Linux
host could compile for Haiku as a target, that's interesting.
Seems like the big tasks are:
1) Haiku VM for continuous integration. Is this hosted in Amazon or other
cloud infrastructure?
2) Supporting aspects of the qemu code
On 25/06/2021 06.12, Richard Zak wrote:
Hello there! I noticed the message which appears when building qemu on
Haiku. I'd hate for Haiku to lose qemu, so I would like to help!
What is needed in terms of a build system for continuous integration? I'm
not familiar with CI systems, other than sim
