Re: Git workflow discussion

One think I did, but it's not possible with apache.org's own git as it's currently organised, is to copy the .svn directory inside the git repository. Then you have best of both world, quite convenient, I found not drawbacks so far. Jacques Le 27/06/2014 01:26, Adam Heath a écrit : That's the

Re: Git workflow discussion

That's the problem, using git for just this one problem. If you do things thru git, then eventually multiple people will have committed code into this new feature branch. After some amount of time, the branch will be done, and it'll be time to add it back to subversion. When this occurs, the

Re: Git workflow discussion

The ASF has its own git setup. Have a look at: http://git.apache.org/ https://git-wip-us.apache.org/ Apparently, both the repositories at the ASF and at GitHup are read-only. Pierre Pierre Smits *ORRTIZ.COM * Services & Solutions for Cloud- Based Manufacturing, Professi

Re: Git workflow discussion

I was only suggesting for the problem at hand... Jacques Le 26/06/2014 21:56, Adam Heath a écrit : Moving to the list, to discuss git. Using the github url for git work, when you need to commit back into svn, is not tenable. I don't think it necessary to rehash the reasons why, it's a well

Git workflow discussion

Moving to the list, to discuss git. Using the github url for git work, when you need to commit back into svn, is not tenable. I don't think it necessary to rehash the reasons why, it's a well known problem in the git-svn space. However, if ofbiz switched to git, then what would be the proced