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.
Thanks, Enoch.
commit 112d45a5e68d615ec2add1902d7d02fefd722817 (HEAD -> 4.14-rt, tag:
4.14.71-ti-rt-r79, origin/4.14-rt)
4.14.71-ti-rt-r79 bb.org_defconfig
4.14 TI Delta:
https://github.com/RobertCNelson/ti-linux-kernel/compare/94bc2c7230f44abaa297c44d916ecfb894246a63...c11ae464608dbf8dcb7e1318b863cb069364ad96
commit 9a3f61575dcd15c9a484659204ef0cf3841c1c61
4.14.71-ti-rt-r79 patchset
On Friday, October 5, 2018 at 5:40:22 AM UTC-4, Luther Goh Lu Feng wrote:
>
> 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
>> [email protected]:beagleboard/linux.git
>> Each time this repository gets updated my git-pull creates numerous
>> unmerged files to resolve by hand.
>> No other git project that I track (including linux-stable) behaves the
>> same.
>> Can this be avoided?
>>
>> Thanks, Enoch.
>>
>>
>>
>
--
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/1b2a649c-5334-481f-825b-c7adc4e11554%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
