Alexandre Oliva wrote:
> On Jan 19, 2001, "Derek R. Price" <[EMAIL PROTECTED]> wrote:
>
> > Harlan Stenn wrote:
>
> >> - on checkin, check the files in with the timestamp on the "local" file
> >>
> >> - on checkout/update, get the list of files that will be "messed with"
> >> and simply do the work in oldest -> newest order
>
> >> - Will this work?
>
> > Yes, as long as the client and server can agree on the time.
>
> Not really. It's quite common that, even when a dependence file is
> modified, a generated file that depends on it doesn't change (think of
> config.h.in, when the modified configure.in hasn't introduced nor
> removed any AC_DEFINEs). In this case, it won't be checked in (unless
> someone pushes for it). Thus, even if CVS were smart enough to retain
> relative timestamps globally, it would still get this case wrong.
Well, you have to use the force option to cvs commit ('cvs ci -f') to commit
any file with a changed timestamp - just like I was until recently with the
CVS sources before Larry Jones reminded me that it really only affected a
fresh checkout :) (anyone know how to make the grin on an emoticon wry?).
I was assuming a forced commit of files with changed timestamps and assuming
Harlan was assuming it, but you're right, I probably should have been
explicit.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
OPHELIA Could beauty, my lord, have better commerce
than with honesty?
HAMLET Ay, truly. For the power of beauty will sooner
transform honesty from what it is to a bawd than the
force of honesty can translate beauty into his likeness.
This was sometime a paradox, but now the time gives it
proof. I did love you once.
OPHELIA Indeed, my lord, you made me believe so.
- Hamlet, Act III, Scene 1, Lines 109-116
