git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Question re. git remote repository

From
DLDavid Lang <david@lang.hm>
Date
Jan 17, 2013, 00:21 UTC
Message-ID
<alpine.DEB.2.02.1301161617240.21503@nftneq.ynat.uz>
In-Reply-To
<A0DB01D693D8EF439496BC8B037A0AEF322098A4@xmb-rcd-x15.cisco.com>
On Wed, 16 Jan 2013, Matt Seitz (matseitz) wrote:
Show 9 quoted lines
> "David Lang" <david@lang.hm> wrote in message news:<alpine.DEB.2.02.1301161459060.21503@nftneq.ynat.uz>...
>> But if you try to have one filesystem, with multiple people running git on their
>> machines against that shared filesystem, I would expect you to have all sorts of
>> problems.
>
> What leads you to think you will have problems?
>
> Why would there be more of a problem on a network file system as opposed to 
> local file system that can be accessed by multiple users?

There are safety checks and synchronization primitives that work between mulitiple users on one machine (where you can see what other processes are running for example) that don't work with separate machines using a filesystem

> Linus seemed to think it should work:
>
> http://permalink.gmane.org/gmane.comp.version-control.git/122670

well, he knows git better than I do, but using git over NFS/CIFS is not the same as saying that you have multiple users on different systems making changes.

In the link you point at, he says that you can have problems with some types of actions. He points out things like git prune, but I would also say that there are probably race conditions if you have two git processes that try to change the HEAD to different things at the same time.

Show 10 quoted lines
> And "git init" specifically has a "shared" option:
>
> --shared[=(false|true|umask|group|all|world|everybody|0xxx)]
>
> Specify that the git repository is to be shared amongst several users. This 
> allows users belonging to the same group to push into that repository. When 
> specified, the config variable "core.sharedRepository" is set so that files 
> and directories under $GIT_DIR are created with the requested permissions. 
> When not specified, git will use permissions reported by umask(2).
>

I think this is dealing with multiple users _reading_ a repository, not making updates to it at the same time.

David Lang
Previous: Matt Seitz (matseitz)Next: Matt Seitz (matseitz)
Message 2 of 8 in “Re: Question re. git remote repository”
  1. Matt Seitz (matseitz)Jan 16, 2013
  2. David LangJan 17, 2013
  3. Matt Seitz (matseitz)Jan 17, 2013
  4. David LangJan 17, 2013
  5. Matt Seitz (matseitz)Jan 17, 2013
  6. David LangJan 17, 2013
  7. Matt Seitz (matseitz)Jan 17, 2013
  8. David LangJan 17, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.