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

Re: How to deal with such reference situation(reference to another project)?

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Sat, 11 Dec 2010 09:41:25 +0100

On 11.12.2010 02:51, albert kong wrote:
> My repository layout is such like
> proj1 proj2
> |---protocol |--
>
> proj2 is dependent with proj1, now in proj2 I need to use protocol code and modify from it. If I only copy code from proj1->protocol directory to proj2, and If I found bugs in the code I can merge bugfix from proj2 to proj1, but I can't see revision infomation of protocol already has in proj1.
> So what's the best practice?

Include the protocol folder with svn:externals property:
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-howto-common-projects.html

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2689830
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-12-11 11:34:34 CET

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