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

Re: Reducing "out-of-date" errors

From: Daniel Rall <dlr_at_collab.net>
Date: 2006-08-01 20:34:11 CEST

On Tue, 01 Aug 2006, Garrett Rooney wrote:

> On 8/1/06, Mark Phippard <markp@softlanding.com> wrote:
> >One thing is clear, in a standard multiple developer scenario with a
> >variety of commits happening from multiple sources, then the current
> >behavior is correct and probably cannot really be improved much. I am not
> >suggesting that Subversion is broken or took a short cut.
> Well, the "we only bumped by one, lets increment everything" case may
> simplify things, but as soon as people have tags or branches or
> anything beyond the utterly trivial case of one working copy and one
> project they're still going to hit the problem, should we add
> complexity to the codebase just to help a case that happens virtually
> never?

You underestimate how often this situation arises in simpler
Subversion deployment scenarios.

I'm not saying "do it", just pointing out that in my experience, this
is not an uncommon situation or use case.

  • application/pgp-signature attachment: stored
Received on Tue Aug 1 20:36:59 2006

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.