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

RE: copies of include files

From: Robert Hunter <robert.hunter_at_gen-i.co.nz>
Date: 2005-01-19 01:56:14 CET

> I have an "include" folder which I would like to use with many of my php
> projects. Every copy of this folder and its content must be same.
> Merging after updating a copy of this folder won't work because I have
> to do it manually. I can forget one or two copies to be merged and
> things go chaotic.

svn:externals sounds like it fits the bill.

Take a look at the section on Externals Definitions in
Chapter 7 ("Advanced Topics") in the Book.

http://svnbook.red-bean.com/en/1.1/ch07s03.html

What I'd like to know is the "best practice" for migrating from
a regular folder to an svn:external. Is it a four-part
[remove, commit, add external property, commit] process?

I've tried doing it all in one go in the past, and found that
updates don't work as expected. (haven't done it for a while,
I will try to reproduce later)

Any pointers?

-- 
Robert Hunter
*****************************************************************************
This communication, including any attachments, is confidential.
If you are not the intended recipient, you should not read it
- please contact me immediately, destroy it, and do not copy
or use any part of this communication or disclose anything about it,
Thank you.
Please note that this communication does not designate an information system
for the purposes of the Electronic Transactions Act 2002
******************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 19 02:00:54 2005

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.