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

FeatureRequest: Improved svn:externals handling on Merge

From: Marcel Hesselbarth <hessi9_at_yahoo.de>
Date: Fri, 20 Jul 2012 16:16:11 +0100 (BST)

Hi developers,

searching the mailing group seems like no posted my problem before, even if Google presents several hits.

The basic problem I have is I have a Project with svn:externals defined pointing into the same SVN. When I now make a commit the files changed inside the svn:externals folders are included - so all works great.

If I now try to merge these commit into a other checkout the changes inside the svn:externals are not merged. I need to do a separate merge at the svn:externals folders. Doing so works fine, but why I have to do this manually?
The merge of svn:externals is not done automatically independent of if the folder at the merge target is an linked svn:externals folder or a real folder. Or what I'm doing wrong?

Now some additional information to the use case:
Of cause I want to use these feature to share common code through svn:externals. I know google will tell me this is no good idea, but unfortunately don't come up with a better solution for organizing the source code. The only idea for avoiding svn:externals I found up to now is to build a common used dll first and embed these dll. Unfortunately this is not possible, as some parts of the shared source code need to be individually compiled into several dll's from the shared and the not shared areas.

So what do you think about this feature? I think it is the missing part at using svn:externals for efficient source code sharing...

With kind regards,
  Marcel Hesselbarth


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-07-20 17:18:00 CEST

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

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