Hi,
We are trying to develop a in-house CVS webtool for all our developers
and content people (we're in web development). The following problems
have arisen:
1) If you check in sources with wrong permissions (for example you
forgot to set x-permissions) you have to manually chmod the file under
[EMAIL PROTECTED] wrote:
> 1) If you check in sources with wrong permissions (for example you
> forgot to set x-permissions) you have to manually chmod the file under
> /var/cvs. But because the file is owned by the last changer, you
> cannot do this from the webtool. Are there any other ways (th
>1) If you check in sources with wrong permissions (for example you
>forgot to set x-permissions) you have to manually chmod the file under
>/var/cvs. But because the file is owned by the last changer, you
>cannot do this from the webtool. Are there any other ways (through CVS
>commands) to chan
Robert-Jan Elias wrote:
> "Derek R. Price" wrote:
>
> > [EMAIL PROTECTED] wrote:
> >
> > > 1) If you check in sources with wrong permissions (for example you
> > > forgot to set x-permissions) you have to manually chmod the file under
> > > /var/cvs. But because the file is owned by the last chan
On Tue, Jan 23, 2001 at 10:30:33AM -0500, Derek R. Price wrote:
> > I don't think so. You have to be owner (or root) to change the permissions.
>
> Well, that seems a little silly as the following makes you the owner if you have
> write permissions to the directory:
But this is what is enforced
On Tue, Jan 23, 2001 at 09:06:01AM -0500, Noel L Yap wrote:
> You can:
>cd $CVSROOT/module_dir
>cp -p archive,v archive,v~
>mv -f archive,v~ archive
And make sure that archive,v is not modified via cvs between
the cp and the mv command.
Ingolf
--
Ingolf SteinbachBalin@I
Larry Jones wrote:
> Derek R. Price writes:
> >
> > cat afile,v >afile,v.new
>
> You have something against the cp command? :-)
Well, I did initially. By default it preserves permissions on my
system. I guess it shouldn't really matter in the above case since
Robert was going to have to c
>> I don't think so. You have to be owner (or root) to change the permissions.
>
>Well, that seems a little silly as the following makes you the owner if you
have
>write permissions to the directory:
>
>#! /bin/sh
>cat afile,v >afile,v.new
>mv afile,v.new afile,v
If you peek under t
