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

Re: Locking binary files

From
Alex Riesen <raa.lkml@gmail.com>
Date
Sep 23, 2008, 14:28 UTC
Message-ID
<81b0412b0809230728p4e81572bg67a3bec4c32c7dfb@mail.gmail.com>
In-Reply-To
<94c1db200809230656q4a9a765dw2354c0058b1d940c@mail.gmail.com>
2008/9/23 Mario Pareja <mpareja.dev@gmail.com>:
Show 5 quoted lines
>> So it's a communication issue then.
>
> Yes, but I think the communication of this information needs to happen
> as part of a developers normal work-flow rather than requiring them to
> remember to check an external system.

Look at pre-receive and update hooks. They can deny a push operation and get enough information to notice a change to the path of your unlucky file.

And yes, *you* have to do that yourself.
Previous: Mario ParejaNext: Daniel Barkalow
Message 10 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.