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

Re: lock

From
PTPaolo Teti <paolo.teti@gmail.com>
Date
Nov 11, 2005, 16:48 UTC
Message-ID
<34a7ae040511110848o624569cah@mail.gmail.com>
In-Reply-To
<20051111164101.GV30496@pasky.or.cz>
2005/11/11, Petr Baudis <pasky@suse.cz>:
> Do you want to lock the file so that noone else will be able to check it
> out? That's impossible from GIT's very nature of distributed version
> control system.
No! I know that is impossible using GIT
Show 5 quoted lines
> Do you want to lock the file in your working copy so that you won't be
> able to remove it or change it? In that case, this is possible, but not
> implemented yet. Part of the solution would involve making the file
> read-only, the rest would be probably to make sure all the tools handle
> that case gracefully.

Yes! this is my case.. The as work-around I can use an hook (i.e. a kind of ClearCase trigger). But remain a work-around!

Previous: Petr Baudis
Message 4 of 4 in “lock”
  1. Paolo TetiNov 11, 2005
  2. Johannes SchindelinNov 11, 2005
  3. Petr BaudisNov 11, 2005
  4. Paolo TetiNov 11, 2005

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.