[LLVMdev] svn mirror git?

[dag at cray.com]

Sean Silva <silvas at purdue.edu> writes:

>>> I agree that if you aren't developing with git for the local branch,
>>> then it would be insanely painful
>>
>> That is exactly the situation I am in.  I have tried to change this many
>> times but it is out of my control, unfortunately.  Yet I keep trying.
>> :)
>
> I'm glad you're persevering! You will eventually succeed :)

Let's hope so!  :)

>> I'm not saying that LLVM should switch to git because of my situation.
>> I'm simply highlighting the way things are now and expressing that the
>> LLVM community is missing out on a bunch of improvements we've made
>> because it is so darn painful to merge.
>
> I think you might be jumping the gun on the conclusion here. Rather
> than pinpointing painful merging as the direct cause, I would more
> generally say that the problem is that you haven't found a way to
> effectively coordinate your internal development so that it results of
> your development can be contributed upstream in a timely manner. You
> might need to get creative.

There certainly is some of that issue but the reality is that we have
deadlines and we have to hit them.  Unfortunately, sending things
upstream is always a lower priority than some other critical customer
need.  It's not what I would prefer, but it's reality.

Hopefully I will be able to do some upstreaming work late this year and
early next year once my immediate goals are finished.

> This is something I hadn't considered (the branch sharing), but it's a
> really good point. Since I'm not currently developing my changes in
> collaboration with other developers, I haven't experienced this.
> However, I can think of a good way to circumvent the problem; it comes
> from the following observation: git-svn is simply your gateway to
> physically creating the revisions in the central SVN repo and fetching
> new revisions, but otherwise need not condition your development. I
> think that the issue that you are running into is that you have
> misplaced the "gateway" to be too close to your everyday team
> development.

That is in fact how *I* work and it works well.  The issue is teacing
everyone else how to work.  We have very few git experts (or even users
at this point) so I don't want to complicate the process.  If you follow
the advice in, say, "Pro Git" you will make a mistake.  I am making
copious notes for the time when we do transition to git, however.  :)

Thanks for your suggestions.  It's nice to have someone to bounce ideas
off.  :)

                            -David