"Greg A. Woods" <[EMAIL PROTECTED]> writes: > [ On Wednesday, February 2, 2005 at 15:33:28 (-0800), Mark D. Baushke wrote: ] > > Subject: Re: CVS diff and unknown files. > > > > Greg A. Woods <[EMAIL PROTECTED]> writes: > > > > > > Yes -- we are in almost full agreement, but it cannot use '-n'. (no > > > commitinfo scripts are run with '-n' and I don't think they should be or > > > ever need to be) > > > > I believe this statement does not reflect the current state of cvs. > > You're right of course. "cvs -n commit" does contact the server (as it > should of course) and it does run any "commitinfo" scripts. I was no > doubt confusing "commit" with "add" when I made that claim. > > But this just makes it even easier to answer Paul's idea for a server > based technical control over file naming. He simply needs to write a > commitinfo script that checks new names against his file naming policies > and then instruct his users to "cvs -n commit newfile" whenever they > want to check their new filenames against the server's policies. They > don't have to commit empty files and they don't have to > > In fact his new customized CVS client could even combine these > operations, and any wrapper/front-end program could trivially do so as > well.
Greg, I tried hard indeed to explain exactly this to Paul. It's hopeless. He doesn't buy the idea, -- he just can't forget his favorite "add-time triggers". -- Sergei. _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs