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

Re: Stale logs and upgrading to WC-NG

From: Greg Stein <gstein_at_gmail.com>
Date: Thu, 9 Apr 2009 03:01:24 +0200

On Thu, Apr 9, 2009 at 00:42, Talden <talden_at_gmail.com> wrote:
>> Nah. But it *might* be worthwhile to cobble up a separate program for
>> this one-off conversion. It's largely a psychic crutch, but might be an
>> important one since in this case,  unlike with previous WC upgrades,
>> there really is no way back (or so I assume).
> And IMHO I'd have that separate program know enough to bring the WC
> into a clean state first (such as dealing with the logs)...
> This separate program should continue to be packaged with the client
> until such time as pre 1.7 WC upgrade is deemed unsupported.

Well... I'm not really in favor of a separate program. I really don't
see the justification over simply have svn do it.

Regarding upgrading: I believe we should always be able to upgrade any
production release. IOW, upgrade 1.0 working copies. I think it is
simply part of our compatibility story across 1.x releases.

The question at hand isn't so much upgrading as "should we expend the
effort to run stale logs from within the 1.7 codebase, or send people
back to a prior release to clear those out first?" (or they can just
do a new checkout) Running stale logs would be a HUGE effort, and
potentially affecting mere handfuls of people. Thus, the reason for
Hyrum's email.


Received on 2009-04-09 03:02:12 CEST

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