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

Re: ISO-8601 dates still

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-05-19 17:07:19 CEST

Nuutti Kotivuori <naked@iki.fi> writes:

> And the third choice is to do what I mentioned in the very beginning -
> make a revision that understand the new timestamps, but produces old
> timestamps still. And then postpone the timestamp changing until a new
> bootstrap tarball is released naturally.

This sounds like the best strategy, as you mentioned earlier:

"Phase 1": libsvn_wc understands both kinds of timestamps. It writes
new-style timestamps to the entries file, but sends old-style
timestamps over the network. Hopefully this can be done before the
pre-alpha milestone.

"Phase 2": after we upgrade our server for pre-alpha, the client can
start sending new-style timestamps to the server.

The issue, as you pointed out, is that it would be bad to have recent
revisions with new-style timestamps on them; it means older clients
would choke when they tried to update. The server should never be
sending new-style stamps until there's a new tarball out there that
can deal with them.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 19 17:11:00 2002

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.