Re: Vendor branches/fork

On May 17, 2009, at 12:40, Stefan Sperling wrote:

> Managing a vendor branch as described in the book is done to avoid
> all this work, yes.
>
> You should also take a look at svn-load, which is a replacement
> for svn_load_dirs.pl: http://free.linux.hp.com/~dannf/svn-load/
> Because svn_load_dirs has no license we may stop distributing it in
> the future.
>
> You could also give mercurial patch queues a look, especially if you
> intend to send patches to the upstream project. It's a slightly
> different
> approach to the vendor-branching problem:
> http://hgbook.red-bean.com/read/managing-change-with-mercurial-
> queues.html

There is also Piston, but I haven't been successful in installing it
on my system so I can't give you a first-hand review...

http://piston.rubyforge.org/

Its tagline is "Ease your vendor branch management worries" so that
could be just what you need.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2295953

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-18 04:26:29 CEST