And I will say this: I know it's not horribly important, but switching to git, especially without using something like github, is almost a non-starter for a Windows Perl user.
The reason being that Msys-git (the one native version of git for Windows) installs its own perl and throws it in the path, which is not a good thing. I've had to support someone on #win32 who didn't realize that at first. Two versions of Perl on the system create weird problems. Adam knows this. That may change in 6 months, but right now, I'd have to throw msys-git in another virtual machine and then transfer the downloaded directory between VM's (or from the VM to the host) to test and work on. Github makes this not so important (because of its ability to download tarballs and edit on the web site) but it's still a pain to have to make all your changes again on the web site after working on them on my machine. And using git sans github (say, the perl5 interpreter repository) is even more of a pain. -0.1 (I'm in the changelog, but I'm not a regular contributor, so I think I can at least speak up...) On Sun, 14 Jun 2009 23:35 +1000, "Adam Kennedy" <adamkennedybac...@gmail.com> wrote: > 2009/6/14 Michael G Schwern <schw...@pobox.com>: > >> Just noting that it's not necessarily all rainbows and puppies, so if > >> svn is working fine it's not compulsory that you move. > > > > Fortunately github lets you download a tarball or zip of any commit or tag. > > No version control software required. > > I meant more interacting with the version control, rather than the > just exporting a single point in time. > > Adam K -- Curtis Jewell swords...@csjewell.fastmail.us %DCL-E-MEM-BAD, bad memory -VMS-F-PDGERS, pudding between the ears [I use PC-Alpine, which deliberately does not display colors and pictures in HTML mail]
