git repository setup

git repository setup

[adamantium84]

Hi, my company is looking to move away from cvs and git was one of the
options. The problem that we have is that our file structure looks like
follows, each of these directories have hundreds of programs some which
would be modified by various programming units.

/x1/system/
/x1/config_apps/
/x1/drivers/
/x1/web/apps/

What we were hoping to have was one repository for "x1" and then have
separate sub repositories for each of the extra areas. So that if there are
any developers needing to change a sub repository then they could without
affected the other sub-repositories and without having to have a copy of the
x1 repository on their systems. From what I have read most of the
documentation suggests that there be one repository and then it gets cloned
to a developers repository, this would be a challenge as the storage
requirements to do this would be rather large.

Would anyone have any suggestions on what to do? or if this would be
possible?

Thanks,
Adam
-- 
View this message in context: http://old.nabble.com/git-repository-setup-tp29078904p29078904.html
Sent from the git mailing list archive at Nabble.com.

RE: git repository setup

[Tim Mazid]

Hi Adam,

I am certain that a more experienced giter will correct me where I err, but I believe that that would only be the case if you put x1 in a single repository.

Will anybody actually need to have the entirety of x1?

The best thing to do would be to create a separate repository for each project, then if needed, create a repository for x1 which has all the other repositories as submodules if you need a single repository containing all the others.

You can enter "git help submodule" for the man page on submodules.

Regards,
Tim

----------------------------------------
> Date: Mon, 5 Jul 2010 12:19:08 -0700
> From: adamkurjewicz@yahoo.com
> To: git@vger.kernel.org
> Subject: git repository setup
>
>
> Hi, my company is looking to move away from cvs and git was one of the
> options. The problem that we have is that our file structure looks like
> follows, each of these directories have hundreds of programs some which
> would be modified by various programming units.
>
> /x1/system/
> /x1/config_apps/
> /x1/drivers/
> /x1/web/apps/
>
> What we were hoping to have was one repository for "x1" and then have
> separate sub repositories for each of the extra areas. So that if there are
> any developers needing to change a sub repository then they could without
> affected the other sub-repositories and without having to have a copy of the
> x1 repository on their systems. From what I have read most of the
> documentation suggests that there be one repository and then it gets cloned
> to a developers repository, this would be a challenge as the storage
> requirements to do this would be rather large.
>
> Would anyone have any suggestions on what to do? or if this would be
> possible?
>
> Thanks,
> Adam
> --
> View this message in context: http://old.nabble.com/git-repository-setup-tp29078904p29078904.html
> Sent from the git mailing list archive at Nabble.com.
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
 		 	   		  
_________________________________________________________________
New, Used, Demo, Dealer or Private? Find it at CarPoint.com.au
http://clk.atdmt.com/NMN/go/206222968/direct/01/