---Chris Burke wrote: > bill lam wrote: > > On Tue, 24 Feb 2009, Alex Rufon wrote: > >> Tried moving to GIT but I've met some resistance from the current > >> users. Currently, were using TortoiseSVN and AnhkSVN so until GIT > >> comes out with parallel products ... I'm stuck. Also, I have no > >> control on the other dev team and they are hosting their own > >> repository in the Manila machines ... I'm in Makati. > > > > You don't have to control the central repository or co-operation from > > other team memebers. For example I > > 1. checkout the J svn repo using git svn clone, > > 2. update from svn repo using git svn rebase > > 3. commit to svn repo using git svn dcommit > > I second this. On Bill's advice, I moved to git several months ago and > never looked back. > > In particular, the git svn interface is really nice. For example, it > allows you to subset projects from a large project like the J Adddons, > into their own git repository. > > At one time I was thinking we might move the Jsoftware repositories > from > svn to git, but the git svn interface works so well that this is really > unnecessary. Just move your own stuff to git, and continue with svn for > the commit to production.
I've been using git for personal projects too, but the current version of git for Windows (MsysGit) has had the git svn interface removed from the end user distribution - so I'm still using TortoiseSVN too. http://code.google.com/p/msysgit/ Known issues ------------ git svn is excluded from the end-user installer because it does not reliably work (see discussions on the mailing list). If you want to use git svn you can install the full msysgit developer environment, as explained on the msysgit homepage. Out of interest there seems to be a TortoiseGIT project that is making good progress, I haven't tried it yet. http://code.google.com/p/tortoisegit/ ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
