Hmm, to be honest, I don't see this argument. Because you can also use a centralised model with GIT.
Also, the main benefit of GIT is not only that you can do offline commits, but mostly that it's sooo much easier to merge! I had a merge hell with my colleague in the company this week. He kept a SVN feature branch for only one week and merging his feature branch into the trunk (team with 10 developers) did cost us a whole day... The reason is that SVN applies an end to end diff while git aims to merge by walking the commit tree of the branch and applying each commit separately. GIT even supports signing off commits. So each committer who pushes to the central repo 'signs' that the contribution is ASL licensed. LieGrue, stru --- On Thu, 9/30/10, Noel J. Bergman <n...@devtech.com> wrote: > From: Noel J. Bergman <n...@devtech.com> > Subject: RE: Podling to use native git > To: general@incubator.apache.org > Date: Thursday, September 30, 2010, 11:13 PM > > Does any other podling use > git-only workflow. > > No ASF project is permitted to use git-only. And the > typical git workflow is part of the problem. We > strongly believe in a single, central, repository as part of > the process of community building. The git model is > better suited to disparate groups partially sharing a > codebase. > > Fundamentally, we WANT people working in a central, shared, > repository. > > If/when the ASF allows git as a technology, you can expect > that the workflow will be an ASF workflow. And once > Greg gets offline commmit working with SVN, I suspect that > it will be harder to push for git. > > --- Noel > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
