git repository setup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]