[LLVMdev] git Status Update?

Chris Lattner clattner at apple.com
Fri Sep 9 13:35:06 PDT 2011

On Sep 8, 2011, at 7:09 PM, Óscar Fuentes wrote:
> Offline commits are useful for Chris when he is on a place without
> internet access. But offline commits are a godsend for people who still
> have no commit rights or for developers who are conducting a series of
> "what if" experiments.

If people need commit access, they should ask for it.  I'm not aware of anyone who is regularly contributing code that hasn't got commit access.

On Sep 8, 2011, at 9:30 PM, David A. Greene wrote:
> Óscar Fuentes <ofv at wanadoo.es> writes:
>> The transition from svn to git is a *social* evolution, not merely a
>> technical one like the migration from cvs to svn was. The convenience
>> of committing while you are in a plane is insignificant compared with
>> the impact such social change can have on the project.
> Thanks Oscar, I think this is exactly right.
> A switch to git is scary because it *is* a shift in how we think about
> the project.

If you're coming at this from the "llvm development processes are broken, we should switch to git so that we can fix them" then I'd claim that you're doing it backwards.  Point out what the workflow problems are, the development processes that should change, and *concrete* and *implementable* suggestions of how to make things better.

Don't make the assumption that switching to git will magically solve all of our workflow/social problems.  A very real problem we have is "not enough reviewers".  I don't see how VCS has anything to do with this very real and present problem.  Lets have a discussion about the real problems, instead of an interminable discussion about git vs svn.

On Sep 9, 2011, at 6:12 AM, Joerg Sonnenberger wrote:
> The barrier of entry for the LLVM.org repositories is low. Getting
> review is normally easy. If it isn't, Git isn't going to improve the
> situation. If a switch to git is desirable to You (not meaning Justin),
> keep in mind that what is easy for one person can create a burden on
> someone else. The LLVM development style exists for a reason and matches
> what many other, often much older and just as large, projects do.


On Sep 9, 2011, at 8:28 AM, Jakob Stoklund Olesen wrote:
> I have been using git-svn for all of the three years I have been imposing my patches on the LLVM project.  I have made maybe 10 commits with svn and 1300 with git-svn. I make offline commits, local branches, and I clean up my patches using 'git rebase -i' before committing.  I couldn't care less if I have to type 'git svn dcommit' or 'git push' to commit stuff.
On Sep 9, 2011, at 9:53 AM, Wesley Peck wrote:
> Just to be clear and upfront, I don't particularly care if the master repository is git or svn. I'm not a full time LLVM developer and I just use git-svn when needed. 

+2:  The main repository being SVN doesn't prevent people who want to use Git or offline workflows from doing so.

These are all reasons why I see the actual switch to git for the main repository to be almost completely unmotivated right now.  Whether git advocates want to admit it or not, there is a *very real cost* to switching.  We have a healthy and active community (which admitted is not without problems) so at least something is working right.

Any discussion of switching to Git should be focused on how it benefits the people who are contributing code on a daily basis, not on how it helps the occasional contributor.  This is not to say that the occasional contributor is unimportant, it is just to say that we shouldn't make it easier for them at the expense of mainstream development.  Further, the occasional developers are not the ones who will ultimately make the call on it, so they're not the ones you need to convince! :)


More information about the llvm-dev mailing list