Just run git-svn on each machine, or copy the repo to the others after you run it. Pull from and commit to the svn repo.
On Sun, May 9, 2010 at 3:53 PM, Joseph Turian <[email protected]> wrote: > Tekkub, > > On Sun, May 9, 2010 at 5:09 PM, Tekkub <[email protected]> wrote: > > Generally speaking, you don't want to do that. git-svn is great for > working > > locally in git and pushing back to an svn repo, or importing (one time) > svn > > to git... but maintaining a two-way mirror will become a huge headache > > because of the way svn works. If the owner of the svn repo isn't willing > to > > move to git then your best best is to just use git-svn locally and not > push > > the repo to github. > > Could you describe the workflow in this circumstance? > Especially if I want to clone the git repository onto other machines? > > -- > You received this message because you are subscribed to the Google Groups > "GitHub" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<github%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/github?hl=en. > > -- You received this message because you are subscribed to the Google Groups "GitHub" 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/github?hl=en.
