Geek asks and answers

Best Rated for Multiple Custom Projects and Git

In my company, we have basic software that is customizable for each client. Today, using SVN, we have this setup:

/trunk
/tags
    …
/branches
    /client_project_x
    /client_project_y
    /client_project_z

What is the best way to organize this in git? Do you have a remote repository for each project and one for the base code, or with a large remote repo with multiple branches?

If we use a large remote repo with multiple branches, is there a way to clone only one branch from a remote repository?

+5
source share
4 answers

, . DVCS , . , - . , . , , . , .

, , .

+2

.

( , git. , .)

+1

git , / , , , , , ! Linux, , , !

, " ", git.

0

:

, :

  • modwork (core)
  • modwork_foo ( "foo" )
  • modwork_app1 (an application that can be installed for multiple clients)

Not a single file in the kernel will be modified during the installation or build process. Each client has the same core. The kernel contains hooks for custom methods.

I do not like changing files in the kernel in branches for clients. I think it becomes difficult if you have more than 5 clients.

0
source

More articles:


All Articles