Err.. disregard.... I figured out how to use this in the manner we desire. Thx
On Tue, Mar 11, 2014 at 2:45 PM, rhugga <chuck.car...@gmail.com> wrote: > > I thought I understood this pretty well until I dug into chapter 4 and > running a GIT server. > > We were looking at taking a approach like this: > > We want a master repo, located on a server and sitting on NAS storage. eg: > /GITREPO > > Each developer will have their own directory under /GITREPO, for example: > > /GITREPO/jsmith > > We don't work on the same files and don't need to worry about merging, > etc... > > I then envisioned each person pulling down a local copy to wherever they > prefer to work from. This might be a backup server, a storage admin server, > their local workstation, etc... I then envisioned them committing their > changes back to the "master repo". So the server holds the "master" copy of > everything. > > Am I going about this wrong? Chapter 4 left me a little confused by > mentioning the server only holds a "bare metal" copy of your project, > basically the .git directory. > > Thx for any info, > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Git for human beings" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/git-users/YMkPuLUgBC4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
