[Top][All Lists]

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

Re: Feature Request: admin files for "cvs import" and "cvs add <dir>"

From: Ralf S. Engelschall
Subject: Re: Feature Request: admin files for "cvs import" and "cvs add <dir>"
Date: Mon, 28 Jul 2003 11:56:11 +0200
User-agent: Mutt/1.4.1i

On Tue, Jul 22, 2003, Wu Yongwei wrote:

> My previous post titled "cvs_acls and cvs import" has got no reply so far,
> and I suppose I should regard it as no one knows of an answer except
> modifying source.
> Thus I request that administrative files for "cvs import" and "cvs add
> <dir>" be added to cvs to control these operations. Not being a cvs guru, I
> just want to give my opinions, and hope that some veteran here could give
> helpful suggestions.
> One way is just to add new administrative files, like "importinfo" and
> "adddirinfo".  If files are too many, maybe some could be merged, say, we
> could use "commitinfo" to check the "add <dir>" operation.
> Opinions?
> (When we can agree on how to change, I can have a try to modify the source,
> if no one else is willing to do it.  But before that I want to hear others'
> opinions on what to do and get advice on how.  I am not familiar with the
> cvs source.)

Admin/info hooks for "cvs admin" and "cvs import" you can find in my
optional "RSE-patches" contained in the OpenPKG package for CVS:

Controlling "cvs add" is currently not supported, but this usually isn't
a big deal. I just run a little cronjob once per day to remove empty
dirs from our CVS repositories...

                                       Ralf S. Engelschall

reply via email to

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