Seems like our svn tree does not fully obey the trunk-branches-tags pattern
In stead of
(1)
trunk/
branches/notation_tool_2/
tags/project_packager_rewrite/
we have
(2)
trunk/rosegarden/
branches/notation_tool_2/
tags/project_packager_rewrite/
If we would strictly obey the trunk-branches-tags pattern, we should have
(3)
trunk/rosegarden/
branches/notation_tool_2/rosegarden/
branches/project_packager_rewrite/rosegarden/
In my opinion, we should choose pattern (1).
This inconformity has also practical consequences, which I found by using
git.
I have trunk checked out and built in directory
rosegarden.git/rosegarden/
Then I want to go to notation_tool_2 branch and type
git branch notation_tool_2
But, alas, the branch will go to directory
rosegarden.git/
while the built files, which are not in the version control, are in
directory
rosegarden.git/rosegarden/
this means that I cannot just use the old build and in the build update only
the files that have changed in the branch.
Therefore, I would suggest that we would start to use properly the
trunk-branches-tags pattern, as is suggested
in page
http://svnbook.red-bean.com/en/1.0/ch04s02.html
if I have understood it correcly.
--
Heikki
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
