[Top][All Lists]

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

Re: Schedule cvs commit at a reqd time...

From: Kaz Kylheku
Subject: Re: Schedule cvs commit at a reqd time...
Date: Fri, 21 Dec 2001 22:17:08 GMT
User-agent: slrn/ (Linux)

In article <address@hidden>, chandrashekar
nagaraj wrote:
>Hi CVS gurus,
>I want to know whether there is a feature
>in CVS to schedule the commit operation
>at a reqd. time, suppose at 6pm everyday.

You are confusing change management and file backup. Your idea is
fundamentally flawed.

Every commit has to be verified for quality. Commits are done when the
developer completes developing and testing a group of logically related

This does not happen at some regularly scheduled times.

Moreover, prior to a commit, the developer must perform an update to
integrate other changes that have occured while he was developing. 
Otherwise the commit won't be able to take place; CVS will stop the
commit with an ``up to date check failed'' error message.

Performing an update to integrate the latest changes into the working
copy may introduce conflicts, or non-conflicting changes which somehow
break the work that has been done so far. So the sanity checks have to
be performed again; this is reiterated until the commit succeeds.

What you can do is tell your developers to update and commit frequently, 
so that the granularity of changes is kept small, and there isn't a whole
lot of valuable uncommitted work sitting on their machines that is not being
backed up.  Back up the *repository* periodically.

If someone needs to develop a substantial chunk of work that cannot be
partially committed into the mainstream due to the risk that it may
destabilize the code, then that developer should consider creating a
branch and commit changes to that.

reply via email to

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