On Fri, Oct 5, 2018 at 9:16 AM Enoch <emc.consulta...@gmail.com> wrote: > > I'll copy the group next time it occurs [as the last update I handled through > lazy cloning and then added my patches]. > I guess Robert Nelson can answer as it must be related to the way he copies > his private kernel repository changes to the Beagleboard public. > Here are his latest two commit messages.
Correct, the "branches" get rewritten on every push, only the "tag's" are consistent. We've got a shared patch-set for many kernel releases, with various patch's in-flight or being nuked from orbit. We are working off a git "base" tree from ti that also has many patches being developed and back-ported from mainline. Plus integration of Aufs, RT, and Wireguard git repo's. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYgyf%3D-BhjzQ54%2B6yZHSpasM7XO5Jt6n3Rv%2Bf2SSNYJk5g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
