If you can, would this work for you?
Create a new project in the repository, eg myarea/vendor/trunk,
myarea/vendor/branches, myarea/vendor/tags
Take a svn export of the current vendor code and put in
myarea/vendor/branches/vendorbranch
svn cp that to myarea/vendor/trunk
Make your modifications in myarea/vendor/trunk
When upstream releases something new, just svn export that code into the
working space you have for myarea/vendor/branches/vendorbranch
svn commit the "changes" that are now in myarea/vendor/branches/vendorbranch
svn merge those changes into myarea/vendor/trunk
?
On Sun, May 17, 2009 at 09:02:11AM -0700, webpost_at_tigris.org wrote:
>Hello all, I'm kinda at an impass right now trying to figure out the best way to proceed.
>
>I would like to customize some software for my own purposes that is hosted by google code, and I am not a developer of that software.
>
>I am trying to figure out the best way to "fork" their code and make my own modifications. More importantly, I would like to be able to sync up to the upstream code without major effort.
>
>I thought that, looking at the handbook, a vendor branch would be the way to go, but I only have read-only access to the repository, and it seems that svn import needs that.
>
>So, is there a svn way to do what I am looking for? I'd really like to avoid having to create a patch, revert changes, update, apply the patch, and reconcile every time I want to update the with the upstream.
>
>Thanks in advance!
>--Ed Z
>
>------------------------------------------------------
>http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2292949
>
>To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-17 19:54:34 CEST