Why not just create a branch in the existing repository? If you need to make it a whole new repository you can disconnect what you checked out from its existing repository before committing it the a new one.
On Thu, Nov 11, 2010 at 12:25 PM, klemens_u <[email protected]> wrote: > Hi everyone, > > I've got a dev-workflow question for you: > > Assume I want to modify/extend an existing symfony project versioned > via svn to which I have no commit access. > > So I begin doing a checkout of the project. > Now I modify or add some files. > But now: leaving the modified files as local changes is no option as I > want to put my changes into a custom repository of my own. > > Any ideas of such a version control "override/extend" feature? > > Can SVK or GIT help with this issue? > > Thanks for suggestions, > Klemens > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony users" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-users%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- Gareth McCumskey http://garethmccumskey.blogspot.com twitter: @garethmcc -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
