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

Re: Locking binary files

From
Dmitry Potapov <dpotapov@gmail.com>
Date
Sep 23, 2008, 20:46 UTC
Message-ID
<20080923204616.GS21650@dpotapov.dyndns.org>
In-Reply-To
<94c1db200809230656q4a9a765dw2354c0058b1d940c@mail.gmail.com>
On Tue, Sep 23, 2008 at 09:56:57AM -0400, Mario Pareja wrote:
Show 7 quoted lines
> 
> The SVN client will make locked files read-only until a lock is
> obtained for them.  This helps "remind" you that a lock should be
> obtained before editing such a file. Requiring the developer to obtain
> a lock ensures that nobody else is editing the file and prevents
> wasted work.  Upon commit, the file is marked as unlocked and the
> local file is once again read-only.

The approach that SVN takes is not only impossible for distributed environment, it does not work even in a _single_ repository where you have branching and merging. If you have a topic branch then your lock will have a zero effect on other developers or lock of other developers on you. Obviously, you are going to have the binary merge conflict at the end. But it is even worse than that. Somebody locked a file on the master branch and you clone from it. Now, this somebody unlocked this file, but this file on your branch remains locked but this person, and this person may even not aware that about your branch. That is insane!

Dmitry
Previous: Dmitry Potapov
Message 19 of 19 in “Re: Locking binary files”
  1. Mario ParejaSep 23, 2008
  2. Andreas EricssonSep 23, 2008
  3. Boaz HarroshSep 23, 2008
  4. Boaz HarroshSep 23, 2008
  5. Mario ParejaSep 23, 2008
  6. Boaz HarroshSep 23, 2008
  7. Dmitry PotapovSep 23, 2008
  8. Andreas EricssonSep 23, 2008
  9. Mario ParejaSep 23, 2008
  10. Alex RiesenSep 23, 2008
  11. Daniel BarkalowSep 23, 2008
  12. Junio C HamanoSep 23, 2008
  13. Daniel BarkalowSep 23, 2008
  14. Dmitry PotapovSep 23, 2008
  15. Daniel BarkalowSep 23, 2008
  16. Dmitry PotapovSep 23, 2008
  17. Daniel BarkalowSep 24, 2008
  18. Dmitry PotapovSep 24, 2008
  19. Dmitry PotapovSep 23, 2008

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.