Hello,

On Thu, Feb 18, 2010 at 22:32:10, Koeller, T. wrote:
> Hi,
>
> being in the early stages of porting the kernel to a new DaVinci-based 
> platform,
> I found that there are two git repositories specifically targeted at DaVinci 
> development,
> namely the one at arago-project.org/git/projects/linux-davinci.git, and 
> another one
> which is at git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-davinci.git.
> This raises the question which one I should use as a foundation for my work, 
> and
> how these trees are related to each other. I tried to apply git to find out 
> about
> that, and came to the conclusion that both trees are mostly independent and no
> merges have recently been done between them. OTOH, active development appears 
> to
> be going on on both trees. Can anyone provide information?

The tree hosted on arago-project.org is contains work in progress
some of which may not been accepted (or even submitted) in mainline
yet. Once the code receives sufficient testing there, it makes its
way upstream through various subsystem tree through patch submissions
(to this list and to other subsystem lists).

The tree on git.kernel.org is maintained by Kevin Hilman who uses
it to host code accepted by him for the next kernel merge window.
He uses this tree to send pull requests to Linus. Sometimes he also
hosts patches accepted on other subsystem trees while we wait for
the trees to merge.

The tree on arago-project.org derives from that on git.kernel.org
plus some non-mainline work.

You will find more functionality on arago-project.org, but the
functionality which has not been accepted upstream may change drastically
by the time the code is accepted mainline.

The wiki page below describes the functionality status on arago-project.org
tree:

http://wiki.davincidsp.com/index.php/DaVinci_GIT_Linux_Kernel_Releases

Thanks,
Sekhar

_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to