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

SV: RE: svn:external Pin on Branch Option

From: Hans-Emil Skogh <Hans-Emil.Skogh_at_tritech.se>
Date: 2007-04-11 17:15:43 CEST

>> It definitely makes sense to pin external revisions when tagging.
>> I would even go as far as saying that externals *always* should
>> be pinned.
> It totally depends on what the external is. In our case,
> we use "internal externals" for shared library projects.

Well, no. It doesn't matter. Having a "floating" external will always
give you a broken history. No way around that.

For example: A colleague tells you of a problem that was detected in
revision 3518 of your main product. This product depends on a number of
shared libraries included by "floating" externals. You update your
working copy to that revision to be able to debug the error. However,
the problem might well not be reproducible on your working copy. If the
error occurs in combination with a specific revision of one of your
shared libraries, and that library has changed since your colleague
checked it out, you're out of luck.

Keep your externals pinned and your history happy, that's my suggestion.
(Even for "internal externals".)


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Apr 11 17:16:44 2007

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

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