<div dir="ltr">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. <div><br></div><div>Maintaining a different branch does not have overhead in git/hg etc. Our team will create a branch per issue and manage it easily.<div><br></div><div>Regards,</div><div>Bharat</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jan 7, 2024 at 4:45 AM R. Matthew Emerson <<a href="mailto:rme@acm.org">rme@acm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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.<br>
<br>
<br>
</blockquote></div>