From harald+jdklists at volse.no Sun Oct 5 19:25:11 2025 From: harald+jdklists at volse.no (Harald Eilertsen) Date: Sun, 5 Oct 2025 21:25:11 +0200 Subject: bsd-port repo organization In-Reply-To: References: Message-ID: Hi Magnus, Thanks a lot for that detailed suggestion. On Tue, Sep 23, 2025 at 04:39:05PM +0200, Magnus Ihse Bursie wrote: > I would recommend, given the circumstances, that you create two new branches > on that repo, named e.g. bsd-port and battleblow. The problem as I see it with the battleblow repos, is that they mainly concern the jdkXXu versions, but do not directly track mainline. > The core idea -- and this is a method shared by other projects -- is to > integrate multiple PRs into the "bsd-port" branch. That way, each individual > PR would be small and easy to review. That is, we will file JBS issues for every PR we want to merge into the `bsd-port` branch, and that this branch is protected so we can't merge anything except through the SKARA workflow? Take care! Harald From harald+jdklists at volse.no Sat Oct 11 08:49:25 2025 From: harald+jdklists at volse.no (Harald Eilertsen) Date: Sat, 11 Oct 2025 10:49:25 +0200 Subject: bsd-port repo organization In-Reply-To: References: Message-ID: On Sun, Oct 05, 2025 at 05:56:48PM -0400, Kurt Miller wrote: > There?s https://github.com/battleblow/jdk which tracks mainline. Right. Just looked rather stale last time I looked at it, but I see it has picked up steam again. That's good! Have been testing it the past few days, and it has some issues on Aarch64 compared to my offline branch, but I'll get that sorted and submitted there too. One issue though, is that it seems to contain contributions from people not covered by the OCA, and as I understand it, that will cause problems when we want this to be upstreamed. Not sure how to deal with that. Take Care Harald