[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bitkeeper-users
Subject:    Re: [Bitkeeper-users] trigger script umask value
From:       Georg Nikodym <georgn () rogers ! com>
Date:       2003-12-10 23:03:34
[Download RAW message or body]

On Wed, 10 Dec 2003 15:21:21 -0700
"Tim M. Sanders" <tsanders@synergymicro.com> wrote:

> I have created a trigger (./BitKeeper/triggers/post-commit.test).  I checked the
> file into my tree.  I cloned the tree and made some changes to a file and
> committed it.  bk tells me that my trigger does not have execute permissions.  I
> explicitly set it (chmod +x) and redit the commit.  Same problem.
> 
> What am I missing?

	bk chmod +x BitKeeper/triggers/post-commit.test
	bk commit -y"Made the post-commit.test trigger executable"

BK stores permissions at the time that they're first put under source
control.

A file that is 0644 when "bk new" is run on it will be 0444 when it is
checked out with a "bk get"/"bk co".

A file that is 0755 when "bk new" is run on it will be 0555 when it is
checked out with a "bk edit"/"bk co -l".

If you need to change perms after the "bk new", then use "bk chmod".
This is a real delta (sccs speak for change) to the file being chmod'ed
that (at some point) needs to be committed to a changeset.

-g

[Attachment #3 (application/pgp-signature)]
_______________________________________________
Bitkeeper-users mailing list
Bitkeeper-users@bitmover.com
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.

[prev in list] [next in list] [prev in thread] [next in thread]