|Re: [hatari-devel] Git commits (was: HDC code update patch)|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Git commits (was: HDC code update patch)
- From: Christian Zietz <czietz@xxxxxxx>
- Date: Mon, 14 Mar 2022 22:15:52 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1647292553; bh=fJGbUmUe8PL0DnwoW3YJ+ShIO3IB5+Yl9NeOZGgIzNE=; h=X-UI-Sender-Class:Date:To:References:From:Subject:In-Reply-To; b=CMQ7DFGag5VJ+QDF8Sn6yio+ULl4mah7eL8abjV804U/YsChVqh/3TUiCUDzxDesW +8G9ndRPDjbbM2lFe4SzYgCQm5N2AIPcinYcDkA0A/xIVFosUpUspbGgrtAdItKTLM X+hHchyNBuEzUAiegb8FDnXxSohVsiyCmH7tPKQY=
Uwe Seimet schrieb:
Using github or gitlab would help with this, and it would also make the
current status, the road to the next release, and the PRs involved more
transparent. And you can create tickets and follow their progress, which is
much more convenient than reporting bugs by email.
The more I write, the more I notice how many useful features I am missing ;-).
I'll let the Hatari maintainers speak for themselves w.r.t. to such a
migration. As a user (and sometimes contributor), I would indeed not
mind if they moved to GitHub, GitLab, etc.  because there are other
things that I don't particularly like about the web interface at
However, for contributions I don't see much of a difference between
doing a few clicks to start a PR on GitHub et al. vs. doing a few clicks
to attached readily formatted patches to an email sent to the list. But
I'm fully aware that this is largely a matter of personal taste. In the
end, it should be the workflow the maintainers and the majority of
contributors feels the most comfortable with.
git simply has too many options ;-).
Here I could not agree more. Unfortunately, git (the command line
client, not the system itself) is not exactly a prime example of a
 Even though moving to a more "commercial" service has its risks.
FreeMiNT and EmuTOS maintainers might remember the Travis CI debacle.
Christian Zietz - CHZ-Soft - czietz@xxxxxxx
PGP/GnuPG-Key-ID: 0x52CB97F66DA025CA / 0x6DA025CA