What is better way to maintain AOSP source code in git repository

Question

I am new to git. We are more then 15 people working on same project.
May I know, what is the better approach to maintain AOSP source code in git repository. I am trying to create setup Git mirror or repo. Generally ,how people will maintain AOSP source code.

Answer 1

AOSP is split over many separate Git repositories and those are managed using a tool called repo.

Think of repo as a manager for multiple Git repositories. It manages checking out the many Git repositories that make up AOSP and you can use it to switch branches (which in turn switches each underlying Git repository to the appropriate branch).

Answer 2

There is one more way. You could take all the code of the AOSP (inc. the kernel) and put it in a big fat git repository.

Its not the best idea, however surprisingly it works well for many phone manufacturers.

Why? Because de-facto Android production code is so tightly coupled between its repositories, and vendor parts are usually tag-specific..

It means however you'll be cherry-picking quite a bit.

Answer 3

Google repo is the best option IMHO. However 3 out of 4 of the companies I'm collaborating with, they have a single, flat, huge git repo. It takes more time and space to creating branches and many other git operations but it works ok