Greg KH wrote:
> On Fri, Jul 17, 2009 at 8:15 PM, Xinyu Chen<[email protected]> wrote:
>>
>>
>> On Jul 16, 10:57 pm, Greg KH <[email protected]> wrote:
>>> On Thu, Jul 16, 2009 at 4:24 AM, Xinyu Chen<[email protected]> wrote:
>>>
>>>> Hi Greg
>>>> Sorry for confusing you. Actually our company, Freescale now wants to
>>>> put i.mx series kernel supporting android to android.git.kernel.org.
>>>> Just like the git: qualcomm kernel/msm.git and TI kernel/omap.git, we
>>>> would like to create kernel/imx.git.
>>>> Then we want to know how to make effort to create kernel/imx.git on
>>>> android.git.kernel.org?
>>> Talk to your Android representative about that, it's a logistics problem.
>> You mean OHA? Freescale has not joined OHA yet.
> 
> Then it might be difficult to get Google to do anything for you :)

Wow. I hope that was sarcasm. As a last resort, you can host your own 
git mirror for the kernel repository.

local_manifest.xml is your friend. I've been using it to "mirror and 
extend" certain git repositories for my research. It works very similar 
to the building for dream instructions 
(http://source.android.com/documentation/building-for-dream) except you 
specify your own "remote" attribute.

For example, you could do:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
   <remote  name="freescale"
            fetch="<git_url>" />
   <remove-project name="kernel/common"/>
   <project path="kernel" remote="freescale" name="kernel/imx" />
</manifest>

I use this technique mainly for an SSH git URL (to share our research 
changes without mirroring the entire Android code base), but there's no 
reason why freescale can't host their own repository to share it with 
the public.

That said, not having to mess with a local_manifest.xml for each device 
variation is a good thing. Please push your changes upstream if at all 
possible.

-Will

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-kernel
-~----------~----~----~----~------~----~------~--~---

Reply via email to