[Top][All Lists]

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

Re: Resend importinfo patch

From: Mark D. Baushke
Subject: Re: Resend importinfo patch
Date: Tue, 28 Oct 2003 23:41:52 -0800

Hash: SHA1

Wu Yongwei <address@hidden> writes:

> Larry Jones wrote:
> >> *I* can accept Larry's opinions if there are ways to limit the
> >> import operation to only some specific persons, say, the PM and the
> >> main developer.
> > Why would you want to do that?  There's nothing you can do with
> > import that you can't do with add, commit, tag, etc.
> It really sounds a strange question. And it is not only I that want this
> feature. However, I'll try to name some reasons:
> 1) To avoid misuse. I once encountered a developer just trying to use
> cvs and importing an existing module. As CVS administrator I do not like
> it at all. Of course he should not do it, but it is better to prevent it
> for ever than to educate everyone, esp. when I am not his boss.

There are reasons that having a importinfo trigger might be useful, one
reason might be that only special approved patches are allowed to be put
into the trunk and cvs import might be able to blow past that

However, this implies you also need to close down the 'cvs add' of a new
directory and the 'cvs admin' of existing files. The exact semantics of
importinfo/admininfo need to be defined so that they make sense to allow
the administrator to define a consistent policy. 

It has been suggested that might make more sense to have commitinfo
called for both import and new directory add operations... that is
another path that is possible and the only reason I lean slightly
against it is that existing commitinfo triggers may not be well suited
to handle these new duties.

> 2) To restrict the creation of modules (and initial files therein).

If you use the commands:

   cvs checkout -l -d dir .
   cd dir
   mkdir new-module
   cvs add new-module

you have just created a new-module top-level module on your server.

        -- Mark
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

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