[LLVMdev] git Status Update?

[David A. Greene]

Bill Wendling <wendling at apple.com> writes:

>> Let's face it, Joe Dragon is pretty much happy with svn and there's an 
>> svn-git bridge for the rest of us.

The svn-git bridge is broken as several people stated before.  It is
easier to contribute code via the gateway but it causes headaches when
one updates one's working git clone after submitting through dcommit.
The git pull generates all kinds of false conflicts.  This is because
svn doesn't understand git history and never will.

git-svn will never be a replacement for git.

> For me, the question is "why do we *need* to switch our versioning
> system?". Nothing is broken with our current model. 

There are things broken with the current model, though you may not care
about them.  It is not possible to conveniently keep a private copy of
LLVM and associated projects and sync regularly with upstream.  It flat
out sucks.  This is because the svn model is fundamentally opposed to
the idea of private repositories.  There's One True Repository and
that's it.

In other words, svn is not a distributed SCM.  It has long struck me as
odd that a project whose license encourages private copies would stick
with an SCM that has no support for keeping such copies.

You may not care, but don't claim the current model is not broken.

> The things I've heard against SVN appear to be relatively minor
> inconveniences. 

I assure you, they are not.

> And we do have a git repo for those who wish to use the newest, most
> fangled thing. :-)

No, we don't.  We have a git-svn mirror which is crippled compared to
native git.

                             -Dave