You can check out an svn repository with git, add a new remote (I believe it has to be git), and then pull the changes from the original svn, and commit to the new git repo.
On Thu, Nov 11, 2010 at 11:25, 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] > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- 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
