|
Message
From: Matjaz Breskvar<phoenix@o...>
Date: Sat Apr 15 10:01:02 CEST 2006
Subject: [oc] kindly convert opencores cvs repository to subversion (svn)
* Jai Dhar (jai.dhar@g...) wrote:
> I don't think anyone has ever regretted the move to SVN; I did it with
> my repository, and haven't regretted it a single moment. I would say
> the biggest advantage is doing away with tagging/branching, and
> replacing that concept with moving/copying of directories. Also,
> regarding web admin., SVN (unlike CVS), is designed for the web in the
> first place, so it integrates well with Apache. My repository is
> located here - http://via.dynalias.org/svn
svn looks very nice, but there is one big problem we would have if we
migrate. (if somebody has a solution, please let me know).
for example in or1k project the following files (in different tools):
or1k/or1ksim/cpu/or32/or32.c
or1k/binutils/binutils-2.16.1/opcodes/or32-opc.c
or1k/gen_or1k_isa/sources/or32.c
(and perhaps some other places i don't remember) should always be in synch
(ie. have identical content). so everytime someone commits changes to any of
these files the changes should automaticaly propagate to all others.
now, with cvs it is easy, these are just hard links. with svn it seams that
something like this is not possible, so a developer would need to always
think to commit in all the different places. if someone has a solution for
this (that would be automaticly) that would really be a big + for svn. there
is a possibility to create a symbolic link, but then you couldn't checkout
just one project (for example or1ksim) but all other depending ones, which
is again a nightmare to remember (there are also other problems with
sym. links)...
the same can be made with whole directories in cvs, so idealy one would
want the same for svn.
best regards,
p.
|
 |
Browse
