{"thread":{"id":"18128","subject":"Lock binairy files in Git","startedAt":"2009-03-04T13:56:48Z","lastAt":"2009-03-04T15:41:40Z","messageCount":3,"participants":["Henk","Johannes Schindelin","Michael Hendricks"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"106975","messageId":"1236175008046-2422894.post@n2.nabble.com","threadId":"18128","inReplyTo":null,"subject":"Lock binairy files in Git","fromName":"Henk","fromEmail":"henk_westhuis@hotmail.com","sentAt":"2009-03-04T13:56:48Z","receivedAt":"2009-03-04T13:56:48Z","isPatch":false,"sender":{"key":"henk_westhuis@hotmail.com","avatar":"https://gravatar.com/avatar/cf9209436cd6db77dded64c77d6afd7a26f776d73b582ef4b3e53df0befae86b?d=mp&s=160"},"body":"\nIn our current version control system we lock binairy files when we edit\nthem. This way other developers know when a file is being edited. Is there\nsomething simular in Git? Or is there another method to let others now I am\ncurrently editing a file?\n\nWe need this only for binairy files, because they cannot be merged. \n\nHenk\n-- \nView this message in context: http://n2.nabble.com/Lock-binairy-files-in-Git-tp2422894p2422894.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"106977","messageId":"alpine.DEB.1.00.0903041512110.8549@intel-tinevez-2-302","threadId":"18128","inReplyTo":"1236175008046-2422894.post@n2.nabble.com","subject":"Re: Lock binairy files in Git","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-03-04T14:15:27Z","receivedAt":"2009-03-04T14:15:27Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 4 Mar 2009, Henk wrote:\n\n> In our current version control system we lock binairy files when we edit\n> them. This way other developers know when a file is being edited.\n\nNo, you cannot.  Git is distributed, and therefore what you want is \nfundamentally impossible.\n\nYou can write hooks, however, enforcing \"locks\", and make your users \ninstall them.\n\nBut due to the fundamental impossibility of the thing, you have to risk \nthat this scenario fails.\n\nIt might be better to come up with a non-tool solution to the problem, \ni.e. appointing people responsible for a certain set of your binary files.  \nThat is outside the purview of Git, though.\n\nCiao,\nDscho\n"},{"id":"106987","messageId":"20090304154140.GA44969@ginosko.grantstreet.com","threadId":"18128","inReplyTo":"1236175008046-2422894.post@n2.nabble.com","subject":"Re: Lock binairy files in Git","fromName":"Michael Hendricks","fromEmail":"michael@ndrix.org","sentAt":"2009-03-04T15:41:40Z","receivedAt":"2009-03-04T15:41:40Z","isPatch":false,"sender":{"key":"michael@ndrix.org","avatar":"https://gravatar.com/avatar/315311e6daa79f24e5648f9534420c24ec48eada42efd4110f1d17167ff44fa8?d=mp&s=160"},"body":"On Wed, Mar 04, 2009 at 05:56:48AM -0800, Henk wrote:\n> In our current version control system we lock binairy files when we\n> edit them. This way other developers know when a file is being\n> edited. Is there something simular in Git? Or is there another\n> method to let others now I am currently editing a file?\n> \n> We need this only for binairy files, because they cannot be merged. \n\nYou can't lock files, but perhaps you could specify a custom merge\ndriver to define how those files should be \"merged\" (for whatever\ndefinition you choose).  See\n\n    http://www.kernel.org/pub/software/scm/git/docs/gitattributes.html\n\nfor details.\n\n-- \nMichael\n"}]}