On Mon, Oct 8, 2018 at 1:59 PM Enoch wrote:
>
> Thanks for demonstrating this git magic.
> Could RCN do the same with Beagleboard/linux branches to introduce non
> conflicting upgrades?
Use this repo instead: https://github.com/RobertCNelson/linux-stable-rcn-ee
Regards,
--
Robert Nelson
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
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
On Fri, Oct 5, 2018 at 9: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
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.
On Fri, Oct 5, 2018 at 9:16 AM Enoch 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
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
I am unfamiliar with how the repo. But it may be helpful to give an idea
what sort of conflicts there are? Maybe in a gist?
--Luther
On Friday, October 5, 2018 at 12:22:26 PM UTC+8, Enoch wrote:
>
> Hi Robert Nelson & Friends,
>
> I have a local Linux kernel repository that tracks
>