info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs add <directory>


From: prakash
Subject: Re: cvs add <directory>
Date: Wed, 21 May 2003 13:52:52 -0700 (PDT)

Thanks!
Is there an interface of some kind which will allow
the files in the repository to be owned by one user
and still allow other users to check-in and checkout.

As of now, files in the cvs repo are being owned by
person who last accessed the file. the same person now
has the capability to go to the file in the CVS repo
and perform actions like chmod. 

--- "Greg A. Woods" <address@hidden> wrote:
> [ On Wednesday, May 21, 2003 at 13:12:34 (-0700),
> prakash wrote: ]
> > Subject: Re: cvs add <directory>
> >
> > So, if someone wants to add a dir to their branch,
> do
> > they use cvs add or is it advisable to use cvs
> import
> > even if the dir is empty when added.
> > basically, trying to code to prevent people from
> > adding dirs to a branch 
> 
> Use of "cvs add" is always best.  Only use "cvs
> import" if you're
> actually tracking third party sources and using the
> vendor branch
> support in CVS.
> 
> Note that directories in CVS (especially in the
> repository) are
> placeholders only.  They simply help to keep files
> in separate places so
> that they don't all clutter the top level.
> 
> Note also that You don't add them to a branch, you
> just add them and
> then they work for all files, on the trunk, or on
> branches, or both.
> 
> "cvs add directory" is currently just a quick
> ``hack'' to allow users to
> create directories in the repository so that they
> may be able to add
> files into those directories.
> 
> -- 
>                                                               Greg A. Woods
> 
> +1 416 218-0098;            <address@hidden>;   
>        <address@hidden>
> Planix, Inc. <address@hidden>; VE3TCP; Secrets of
> the Weird <address@hidden>


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com




reply via email to

[Prev in Thread] Current Thread [Next in Thread]