Thanks for demonstrating this git magic. Could RCN do the same with Beagleboard/linux branches to introduce non conflicting upgrades?
On Friday, October 5, 2018 at 11:31:52 AM UTC-4, David Lechner wrote: > > This is how I do it: > > git fetch beagleboard > git rebase --onto 4.14.71-ti-r79 4.14.71-ti-r78 my-branch > > where "beagleboard" is the git remote for > https://github.com/beagleboard/linux.git, "4.14.71-ti-r79" is the new tag > I am rebasing onto, "4.14.71-ti-r78" is the previous tag my branch was > based on and "my-branch" is the name of the local branch I want to rebase. > > > On 10/05/2018 09:47 AM, Enoch wrote: > > Can you (somehow) make it easier to follow the public Beagleboard kernel > via the usual git-pull and git-rebase processes [to enter one's local > commits] . > *Your work is greatly appreciated. *The vanilla Linux-stable kernel is > simply inadequate to take advantage of the full Beagleboard hardware. > Is there a published recipe explaining how you do this amalgamation? > > Thanks, Enoch. > > On Friday, October 5, 2018 at 10:23:24 AM UTC-4, RobertCNelson wrote: >> >> On Fri, Oct 5, 2018 at 9:16 AM Enoch <[email protected]> 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 [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/d644c304-5ba5-405a-ab3b-885138f92ff1%40googlegroups.com > > <https://groups.google.com/d/msgid/beagleboard/d644c304-5ba5-405a-ab3b-885138f92ff1%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/572d1c6b-2cd4-4e78-a40b-bc7e161ca50b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
