On Friday, May 16, 2014 11:03:26 PM UTC+2, Alain wrote: > > This is what i understood from the book i'm reading, but what i don't > catch (because nothing about it is written) it's about the bare repository > and source repository permissions. >
I'm going to assume source repository means non-bare repository, or a repository with a work-tree. > i understood that bare repository is in fact the content of the .git > directory contained inside the source repository. > Yeah, pretty much. > what i miss it's if you share both to team members ? i mean if you share > (write/read access) to bare repository and source repository. > No, you don't give others access to your work-tree repository. It's on your own computer, and you don't share it. You do your work there, make commits, and push from it. And fetch/pull to it. > team members clone the bare repository, pull, do changes, commit and > push... > but i simulate the situation in the book, where bob change a file and list > change the same file. Now Bob push changed filed and Lisa pull, applied > updated (add Bob's changes + her) and try to push. > however as both are on local "copy" of the repository they can't push it > to origin/master.... (to the source repository) > I'm not sure which book or what page this is, but I'm going to assume Bob and Lisa share a central bare repository on some server. First Bob pushes his change first to the server. Afterwards Lisa does a pull, and gets Bob's changes into her local work-tree repository, and she applies her own changes, and then pushes to the central repository again. This is quite normal procedure with Git. -- 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.
