Re: CVS diff and unknown files.

[Sergei Organov]

"Greg A. Woods" <address@hidden> writes:
> [ On , January 31, 2005 at 20:30:21 (+0300), Sergei Organov wrote: ]
> > Subject: Re: CVS diff and unknown files.
> >
> > Don't you wish to even try to understand the suggestion? The suggestion
> > is: invoke *the same triggers* both at 'cvs add' and 'cvs commit' time,
> > -- there is no need for separate triggers.
> 
> No, using the same scripting hook at both add and commit times would be
> bad, VERY bad.

Sure. But I didn't in fact suggest it. I in fact argue in favor of
absence of add-time hooks on the server at all. Let me try to explain,
as the exact meaning of the suggestion has been somehow lost in the
endless discussion with Paul.

What do we exactly mean by add-time here? The time when "cvs add"
client command is invoked, or the time when new file is to be committed
to the repository using "cvs commit"?

If the latter, that is not the topic of this discussion.

If the former, then server should not care/know about "cvs add" at all,
so there is no such thing as "add-to-working-copy time" from the point
of view of server, so there could be no server hooks invoked at this
non-existing time, so these non-existing hooks can be neither the same
nor different from commit-time hooks. In other words, I believe there
should be no "cvs add" server command at all.

What I actually meant in the phrase you've taken out of contents and
commented against is: iff somebody decides he needs to perform some
checks on the server whenever user adds files to his working copy, he
can arrange to invoke "cvs -n commit" after every "cvs add" (or as
[optional] part of "cvs add"). This effectively makes *virtual*
"add-time hooks" equal to "commit-time hooks" without any server-side
"add-time hooks".

-- 
Sergei.