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

intend-to-edit flag

From
TKThomas Koch <thomas@koch.ro>
Date
Jul 4, 2013, 17:56 UTC
Message-ID
<2240842.MQEMCLPV8Z@x121e>
Hi,

we're evaluating Git to be used in our companies Tool. But a hard requirement is the possibility to set an "intend-to-edit" flag on a file (better path). Notice that I did not use the word "lock"! :-)

One easy implementation might be a special branch "XYZ-locks" that contains an empty blob for every flagged file. So our tool just needs to check, whether a blob exists for the path that's intended to edit, tries to push a commit that touches the file and only allows editing if the push succeeds.

Does anybody have a better idea, maybe with notes?
Thank you,
Thomas Koch, http://www.koch.ro
Next: Ævar Arnfjörð Bjarmason
Message 1 of 4 in “intend-to-edit flag”
  1. Thomas KochJul 4, 2013
  2. Ævar Arnfjörð BjarmasonJul 4, 2013
  3. John KeepingJul 4, 2013
  4. Thomas KochJul 4, 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.