gnu.cvs.help
[Top] [All Lists]

RE: File group attribute after cvs tagging (for users belongs to two gro

Subject: RE: File group attribute after cvs tagging for users belongs to two groups
From: "he yu"
Date: Mon, 11 Sep 2006 10:34:12 +0800
Newsgroups: gnu.cvs.help
Hi, Kevin,

Thanks for your reply.

How about if I would like to make this happen automatically when every time after tagging?

For not every users to this cvs server have the priviledge to logon to the UNIX machins to change the group for the modules.

Thanks in advance.


Regards,
Winnie


From: "Bulgrien, Kevin" <Kevin.Bulgrien@xxxxxxxxxxxx>
To: 'he yu' <heyu0571@xxxxxxxxxxx>, "'info-cvs@xxxxxxxxxx'"
<info-cvs@xxxxxxxxxx>
Subject: RE: File group attribute after cvs tagging (for users belongs to
two groups)
Date: Fri, 8 Sep 2006 11:46:28 -0400

> A user's primary is a, and he is also added to the group b in UNIX > system.
>
> Here's a CVS project A with group attribute a and CVS project B with > group attribute b.
>
> This person works in both projects. When he make tag in project B, > his primary group a is applied to all the files he has tagged in
> project B so
> that cause problem for the other person works in project B.
>
> How could I resolve this problem?

In the CVS repository, modify the permissions of the directories
(modules) and all files and directories under that module directory. The repository directory permissions can be used to control the group ownership of files in the directory. You will have to set the group ownership of the project directories in the repository and they have to be SetGID so that newly created files are created with the same group permissions as the directory they are created in.

For example:

  chgrp -R b /path/to/repository/module
  chmod g+s /path/to/repository/module

If the project contains subdirectories, you will need to change the group permissions of each subdirectory. The following is an example.

  for dir in $(find /path/to/repository/module -type d)
  do
    chmod g+s "${dir}"
  done

The above assumes that the entire project (module) has the same group permissions. Of course, you can customize each module or submodule as needed. Do the same with the a project, but make the directories owned by the group a instead of b.

---
Kevin R. Bulgrien
Design and Development Engineer
VertexRSI


CONFIDENTIAL/PROPRIETARY

Unless otherwise indicated, all information (including attachments) contained in this e-mail communication is confidential and proprietary information exclusively owned by the sender and/or its related or
affiliated
companies and shall not, without the prior written consent of the sender,
be
used, disclosed, distributed or reproduced, in whole or in part, by anyone other than the individual or entity to whom this communication is
addressed
exclusively for the purpose expressly indicated in this communication.

This e-mail communication is intended for the use of the individual or entity to whom it is addressed. If you are not the intended recipient of this communication, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please destroy any copies, electronic, paper or otherwise that you may have.

_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。  http://www.hotmail.com

_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com



<Prev in Thread] Current Thread [Next in Thread>