oleksa borodie <oleksa.borodie@gmail.com> writes:
> I'm using some open-source projects code in my work. I need make
> changes with open-souce code to implement some feature. This changes
> is too specific and cann't be used in the project sometime.
> Is there "the best practice of" maintaince custom changes with new versions?
>
> E.g. os1 - project with my changes based on 1.1 version hosted in the
> local repository. How should I merge local changes with new 1.2
> version? Should I put local changed source code into the separate
> project with original code?
> repository
> -os1 //changed sources
> --trunk
> -os2 // original souces
> --trunk
I believe the contrib/client-side/svn_load_dirs.pl script that ships
with Subversion can help you. It is Subversion's way of achieving the
CVS feature known as "vendor branches", which is essentially what you
want.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 6 20:00:16 2005