[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: timestamp preservation design (issue 1256)

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-06-24 21:24:21 CEST

On Tue, 2003-06-24 at 13:13, Ben Collins-Sussman wrote:
> > It was highly surprising to me when I found out about it as a CVS user.
> Heh, that's funny. So I'm saying that "but CVS users are used to it",
> and you're saying "but that doesn't mean it isn't weird". :-)

Perhaps I was talking past you, sorry. I'll be more explicit: the
behavior may not be surprising to a CVS user who knows what CVS does in
this department (I assert that such people are pretty rare); however,
from experience with CVS, I know that it's surprising behavior in

And, though our primary audience may be CVS users, that's no excuse for
writing in behavior which would be surprising to a new user, just
because CVS made the same mistake.

> * checkouts and updates always use the commit-time
> * updates always use the 'now' time.
> This allows 'make' to work no matter what, even if you do unusual wc
> backdating that involves deletes & adds. Is that a 100% solution?

I think you meant to say "checkouts and exports." I think that solution
is 100% make-compliant, but I don't see how changing the checkout
behavior helps anyone.

> Yeah, I'm on crack, never mind. I was thinking about "release
> managers who create tarballs via 'svn export'".

If this is the only audience your proposal can satisfy, then only the
"export" command should be modified. I'm okay with changing that.
(Especially because we have this nice, separate export editor now.)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 24 21:25:19 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.