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
Patch has all
the details, though the volume of patches means that you really want to
make sure that you CC the maintainers of the code listed in the MAINTAINERS
file when submitting patches to help ensure they do not get list.
Warner
În vin., 25 iun. 2021 la 03:09, Thomas Huth a scris:
On 2
to
> make sure that you CC the maintainers of the code listed in the MAINTAINERS
> file when submitting patches to help ensure they do not get list.
>
> Warner
>
>
>>
>> În vin., 25 iun. 2021 la 03:09, Thomas Huth a scris:
>>
>>> On 25/06/2021 06.1
the maintainers of the code listed in the MAINTAINERS file
when submitting patches to help ensure they do not get list.
Warner
>
> În vin., 25 iun. 2021 la 03:09, Thomas Huth a scris:
>
>> On 25/06/2021 06.12, Richard Zak wrote:
>> > Hello there! I noticed the message
t is
patch information. What's the primary way for code to be contributed, a
merging code though Gitlab or via emailed patches?
În vin., 25 iun. 2021 la 03:09, Thomas Huth a scris:
> On 25/06/2021 06.12, Richard Zak wrote:
> > Hello there! I noticed the message which appears when b
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,
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 simply knowing what they do.
-
