You are really abusing the version control system here.
By not using a vendor import for the external project w32api, you make it much harder to
keep local changes separate from the
non-local changes to w32api and thus complicating the synchronization of the two. This is
what Gé is currently doing with the shared
wine code and eventually all external code should be imported this way to minimize
maintenance.
By re-importing the data from trunk instead of merging it from trunk, you effectively
screw up the versioning. When the time comes
to merge your changes to trunk, you cannot since there is no common history. The only way
to get it to trunk is to use "svn delete"
and "svn copy" and thus you loose any changes made to include/ and w32api/ on
trunk since you created the branch.
I'd suggest you read Gé's introduction at
http://reactos.com/wiki/index.php/Using_code_from_other_projects and
http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-7-sect-4 and do it this way
instead.
Casper
-----Original Message-----
From: ros-svn-bounces(a)reactos.com [mailto:ros-svn-bounces@reactos.com] On Behalf Of
ion(a)svn.reactos.com
Sent: 8. maj 2005 03:31
To: ros-svn(a)reactos.com
Subject: [ros-svn] [ion] 15097: Wipe out current includes to start fresh.
Wipe out current includes to start fresh.
Deleted files:
branches/new_headers/reactos/include/
branches/new_headers/reactos/w32api/
_______________________________________________
Ros-svn mailing list
Ros-svn(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-svn