lock

lock

[Paolo Teti]

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?

Pao

Re: lock

[Johannes Schindelin]

Hi,

On Fri, 11 Nov 2005, Paolo Teti wrote:

> 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?

You should be able to do that with a hook (see Documentation/hooks.txt).

Hth,
Dscho

Re: lock

[Petr Baudis]

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.

Re: lock

[Paolo Teti]

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

> 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!