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

Re: Lock binairy files in Git

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Mar 4, 2009, 14:15 UTC
Message-ID
<alpine.DEB.1.00.0903041512110.8549@intel-tinevez-2-302>
In-Reply-To
<1236175008046-2422894.post@n2.nabble.com>
Hi,
On Wed, 4 Mar 2009, Henk wrote:
> In our current version control system we lock binairy files when we edit
> them. This way other developers know when a file is being edited.

No, you cannot. Git is distributed, and therefore what you want is fundamentally impossible.

You can write hooks, however, enforcing "locks", and make your users install them.

But due to the fundamental impossibility of the thing, you have to risk that this scenario fails.

It might be better to come up with a non-tool solution to the problem, i.e. appointing people responsible for a certain set of your binary files. That is outside the purview of Git, though.

Ciao, Dscho

Previous: HenkNext: Michael Hendricks
Message 2 of 3 in “Lock binairy files in Git”
  1. HenkMar 4, 2009
  2. Johannes SchindelinMar 4, 2009
  3. Michael HendricksMar 4, 2009

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.