Re: [Flightgear-devel] GIT / SVN
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Turner snip - git works great on the Mac, or any Unix, but I believe it's never going to fly (if you'll pardon the expression) on Windows, due to technical limitations there snip FWIW, Cygwin provides git (V1.5.3.5) for Windows systems. I know that the majority of development on Windows is now done with MSVC, but isn't Cygwin still required at the moment for something? Terrasync perhaps? Richard - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GIT / SVN
Richard Bytheway wrote From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Turner snip - git works great on the Mac, or any Unix, but I believe it's never going to fly (if you'll pardon the expression) on Windows, due to technical limitations there snip FWIW, Cygwin provides git (V1.5.3.5) for Windows systems. I know that the majority of development on Windows is now done with MSVC, but isn't Cygwin still required at the moment for something? Terrasync perhaps? Richard Yes, Cygwin is still required for Terrasync, and for patching as well. Its Git utility isn't exactly user-friendly, but if you are used to CVS with Cygwin, the transition to Git isn't difficult. I would guess for most Windows user this is all too much hassle though There is a Windows client for Git: Git-gui, but I can't locate a download site for it atm. I've been using it for a while. It's not brilliant. Tortoise CVS/SVN is much easier. Frankly WinCVS is better than Git-gui, and in some ways better then Tortoise CVS or SVN. I use whichever is more convenient at the time. Vivian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GIT / SVN
On 20 Aug 2008, at 21:14, Frederic Bouvier wrote: Migrating from CVS to SVN would already be a very good thing IMO Just to add some data to this - git works great on the Mac, or any Unix, but I believe it's never going to fly (if you'll pardon the expression) on Windows, due to technical limitations there - git works great with the current setup (read-only repo mirrored from CVS). For local development, if you can, and want to use it, it's pretty nice (I think Melchior has said the same thing) - I'd be quite happy using git's patch submission features to flood people's inboxes with patches :) Although the round-trip delay from creating the patch to it being applied to CVS to getting mirroed to the git repo is pretty long. - I'd also be quite happy publishing a public tree for someone with CVS access to pull / cherry-pick from, and I assume any other 'heavy' git user would similarly be happy publishing their tree. My gut feeling is there should be a 'quick' migration to SVN for data and code, since CVS is just so dreadful - and the migration process is standard, and so are the tools (eg TortoiseSVN on windows is great). Deciding whether the primary code repos should then be git or svn is a more complex debate, but it feels like we'll always need both - git is too complex for some people, even if they're not on Windows. James - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GIT / SVN
For what it's worth, I have started playing around with cvs2svn, but only very recently. I've got nothing anyone can point at yet. Also by the way, I will be out of town for a work project thursday - sunday. Also by the way, my summer soccer team made the playoffs (we had to win our last 5 games of the season to get in, and then just barely.) But we beat the top seed in the first round 6-2 and moved on to the quarter-finals which we won in a shoot out after a 2-2 tie. This is the furthest any team I've played has made it into the playoffs. Now the semifinals and championship games are this weekend and I have to be out of town for a work project. Bummer ... ! But maybe they'll have a chance to win with out me on the field. :-) (I had to say that before someone else did.) :-) Curt. On Wed, Aug 20, 2008 at 4:27 PM, James Turner wrote: On 20 Aug 2008, at 21:14, Frederic Bouvier wrote: Migrating from CVS to SVN would already be a very good thing IMO Just to add some data to this - git works great on the Mac, or any Unix, but I believe it's never going to fly (if you'll pardon the expression) on Windows, due to technical limitations there - git works great with the current setup (read-only repo mirrored from CVS). For local development, if you can, and want to use it, it's pretty nice (I think Melchior has said the same thing) - I'd be quite happy using git's patch submission features to flood people's inboxes with patches :) Although the round-trip delay from creating the patch to it being applied to CVS to getting mirroed to the git repo is pretty long. - I'd also be quite happy publishing a public tree for someone with CVS access to pull / cherry-pick from, and I assume any other 'heavy' git user would similarly be happy publishing their tree. My gut feeling is there should be a 'quick' migration to SVN for data and code, since CVS is just so dreadful - and the migration process is standard, and so are the tools (eg TortoiseSVN on windows is great). Deciding whether the primary code repos should then be git or svn is a more complex debate, but it feels like we'll always need both - git is too complex for some people, even if they're not on Windows. James - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://baron.flightgear.org/~curt/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
