Re: Re: Git Migration: Status Update

+1 Git can be confusing for seasoned Subversion developers at first, as it really is a fundamental paradigm shift in many respects. I'm not sure why you're only able to do read-only access, though. The add/commit syntax for Git is fairly similar to that of SVN. Have you tried creating a dummy repo locally and making commits to that? I'm not privy to the latest on the Git migration project, but it could just be a Git and/or FSO permissions issue on the remote origin. --Kris On Tue, Mar 13, 2012 at 8:18 AM, Richard Lynch <ceo@l-i-e.com> wrote: > On Wed, March 7, 2012 1:51 pm, Sebastian Bergmann wrote: > > Am 07.03.2012 19:46, schrieb Kris Craig: > >> As I and others have said already, using a Subversion branching > >> model > >> on Git just doesn't make any sense. > > > > How often does it have to be explained to you and others that we > > would > > like to do this step by step? First we change the tool, then we > > change > > the process. Shouldn't be too hard to understand ... > > Maybe it's just me, but if I told my boss we were going to change the > tool and decide and document the fundamental business processes later, > I don't think that would float... > > That said, I still can't get my head around Git at all, and so far > have only managed to checkout/update on a read-only basis. Not that it > matters. My code contributions to PHP have been nil so far anyway. > > -- > brain cancer update: > http://richardlynch.blogspot.com/search/label/brain%20tumor > Donate: > > > https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >