Re: timestamp stuff, issue 1445

Ben Collins-Sussman <sussman@collab.net> writes:

> In summary, once I commit this change, the behavior will be:
>
> * 'svn export' always sets commit-times
> * 'svn update' always sets now-times
> * 'svn checkout' can behave either way, based on config variable.

Oh frell. I got the proposal wrong again, misunderstanding ghudson.

The point is: he and Philip don't want a mixture of commit-times and
now-times in their working copies. So ghudson's request is that 'svn
checkout' and 'svn update' always do the *same* thing -- either they
both use now-times, or both use commit-times, and this behavior can be
controlled by user variables.

The first use-case is for developers: they checkout, then update every
day, and need 'make' to work correctly. Especially if they backdate
the working copy, they need the touched files to have 'now' times.

The second use-case might be for developers or websites, where you
only care about commit-times, no matter how many times you update.

So my actual proposal is this:

    * 'svn export' always sets commit-times
    * 'svn update/checkout' uses either commit-times *or* now-time
                             based on config variable.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 5 01:33:09 2003