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

Re: Looking for ideas for a tag/release svn usage model

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Tue, 01 Sep 2009 17:41:12 -0500

Brett Coon wrote:
> On Tue, Sep 1, 2009 at 12:32 PM, Bob Archer <Bob.Archer_at_amsi.com
> <mailto:Bob.Archer_at_amsi.com>> wrote:
> >I understand that. My question is whether or not there's an easy
> way to update an entire work area to a /mixed /set of versions, e.g.
> a one->line way to do the equivalent of:
> >svn update -r1234 somedir/
> >svn update -r1210 somedir/weirdfile.x
> >svn update -r2111 otherdir/dira
> >svn update -r2012 otherdir/dirb
> Why would you want to do that? Generally you want to update to HEAD
> every time.
> I would want to do that if those specific versions were the most recent
> versions that were known to work correctly together (e.g. passed some
> level of regression testing).
> Ideally, those versions /would /be identical to HEAD most of the time,
> since all checkins would pass the regression tests.
> Again, what I'm looking for is a way to update my work area to the
> newest "blessed" version of each file, even if that version happens to
> not be HEAD. It seems there is no directly-supported means to do this.

Can't you (a) copy the known-working (or release) versions to tags for
more sensible reference names, and (b) use externals to pull them into
the appropriate place in your workspace?

   Les Mikesell
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-02 00:42:37 CEST

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

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