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

Re: lock

From
Petr Baudis <pasky@suse.cz>
Date
Nov 11, 2005, 16:41 UTC
Message-ID
<20051111164101.GV30496@pasky.or.cz>
In-Reply-To
<34a7ae040511110831y3e896738o@mail.gmail.com>

Dear diary, on Fri, Nov 11, 2005 at 05:31:31PM CET, I got a letter where Paolo Teti <paolo.teti@gmail.com> said that...

> Just a question probably stupid because I'm a quite new GIT user.
> 
> Is possible to apply a lock (as in ClearCase) on a given file etc in order to
> prevent accidental check-out or any other tool operation?

Can you be a bit more detailed in the description of what do you exactly want?

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.

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.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
Previous: Johannes SchindelinNext: Paolo Teti
Message 3 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.