trunk/kdeedu/klettres
Andras Mantia
amantia at kde.org
Sat Feb 19 11:08:24 GMT 2005
On Saturday 19 February 2005 12:54, Andras Mantia wrote:
> So how can I create a branch in the KDE repository if I want to
> branch the whole kdewebdev?
Ok, I got this working:
svn copy https://svn.kde.org/home/kde/trunk/kdewebdev
https://svn.kde.org/home/kde/trunk/kdewebdev/test-branch -m Trying this
way. -r HEAD
What confused me is that the SVN documentation suggests the layouting in
the following way:
/
project1
trunk
branches
my_branch
project2
trunk
branches
my_branch2
and in KDE you have:
/
trunk
project1
my_branch
project2
my_branch2
I'm not sure which is better. In case of simply doing some
"make_it_cool" thing, the second might be OK, but when a new release is
made and the repository is branched, I'm not sure that either of the
above would be good. In that case maybe a
/
trunk
project1
project2
branches
4.0 release
project1
project2
4.1 release
....
would be better. Well, I don't have any SVN experience, so you gan
ignore it if I talk stupid things. I just try to understand how the
global (release) and developer branching will work.
Andras
--
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050219/942405ac/attachment.sig>
More information about the kde-core-devel
mailing list