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

Adding older vendor releases to an established vendor branch

From: Ryan Lange <ryan.m.lange_at_gmail.com>
Date: Wed, 29 Aug 2012 16:16:59 -0400

Hello again,

As I mentioned in my previous message, I've been thinking about a
repository structure for some personal projects I'll be working on.
Another issue that occurred to me---also related to vendors releases,
but different from the issue in my other message---is what to do when
you decide that you want to test against a version of VendorA's code
that is older than the oldest version in your vendor branch.

For example, your vendor branch currently looks like this:

    - vendors/
         - VendorA/
             - 2.0.0/
             - 2.1.0/
             - current/

This is probably a sign of poor planning, but what if you decide that
you also want to test against v1.0.x of VendorA's code? Does anyone have
any thoughts on how to handle, or experience with handling, such a
situation?

Thanks again,
Ryan
Received on 2012-08-30 00:04:20 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.