Tracking FreeBSD-CURRENT

[Brooks Davis]

On Thu, Sep 03, 2020 at 03:34:32PM +0200, Dmitry Salychev via freebsd-hackers wrote:
> Hi Stefan,
> 
> > Any new code must be committed to -CURRENT first, before it may be
> > merged into the stable branches (and then will make it into a release).
> 
> Is this approach the same for code which is intended for ARM? For
> example, if there is a driver for an ethernet transceiver connected to
> BeagleBone Black. I should track -CURRENT on my laptop, add, build and
> test my driver on BBB, merge the latest changes from -CURRENT and send a
> patch. Am I correct?

If your code is destined for another system, there's little reason to
track -CURRENT on your laptop.  You can easily cross-build -CURRENT from
(e.g.) 12.1 or an older -CURRENT.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20200903/96f6c59e/attachment.sig>