[Openmcl-devel] work in arm64 branch or on main branch?

[Bharat Shetty]

As the source, scripts are all segregated, this should be OK as long as the
common files use the preprocessor directive right. Working from a single
branch will id issues earlier. But instead of main branch you could use a
development branch which syncs/fetches changes as and when they are done on
the main branch. Doing so will keep the releases clean.

Maintaining a different branch does not have overhead in git/hg etc. Our
team will create a branch per issue and manage it easily.

Regards,
Bharat

On Sun, Jan 7, 2024 at 4:45 AM R. Matthew Emerson <rme at acm.org> wrote:

> As I do little bits of work on an ARM64 port, is there any killer benefit
> to keeping that work in a separate arm64 git branch? I was thinking that
> committing to the main branch would make visibility better, and as long as
> the main branch always builds, the overhead of a long-lived branch seems
> not worth it.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20240107/e11684b3/attachment.htm>