[LLVMdev] svn mirror git?

[Sean Silva]

>> Most development is not "some contributor's fork".
>
> Well, in the git model every developer has a fork.
>
>> What you suggest works great for the occasional drive-by
>> contributors, but most development is not from drive-by's.
>
> Not sure what you mean by "drive-by" but in git this is really
> irrelevant, I think.

Sorry for the lack of clarity. I was trying to contrast with the
status quo. By "drive-by" I *roughly* mean "people without commit
access" (i.e. that aren't consistently delivering patches). In his
scenario there is "contributor" and "maintainer". What I was trying to
get across is that most development (in the status quo) is actually
done by people that are closer to the "maintainer" role, so making it
easy for "contributor" is not a gigantic priority; although, (and I
speak from my own experience from before I had commit access), when
you're not a committer, it really *seems* like the "contributor" role
is the only one that matters.

Also, "contributor" is not going to be sending in huge changes, so the
overhead of git-fetch'ing from github or wherever is probably going to
be greater than git-apply of an attached patch.

-- Sean Silva

On Thu, Nov 15, 2012 at 6:53 PM,  <dag at cray.com> wrote:
> Sean Silva <silvas at purdue.edu> writes:
>
>>> For example, say github's llvm-mirror was a contributor's fork.  The review
>>> process might look like this:
>>>
>>> Contributor:
>>>      Please review my patch:
>>> https://github.com/llvm-mirror/llvm/commit/4823be3be1d87632fbd51ce8e51a58ee5e44b115
>>>
>>> Maintainer:
>>>     Adds inline comments with online tool.  Then when patch is looking good:
>>>     $ git fetch https://github.com/llvm-mirror/llvm.git
>>>     $ git cherry-pick 4823be3be1d87632fbd51ce8e51a58ee5e44b115
>>>     $ git push
>>
>> Most development is not "some contributor's fork".
>
> Well, in the git model every developer has a fork.
>
>> What you suggest works great for the occasional drive-by
>> contributors, but most development is not from drive-by's.
>
> Not sure what you mean by "drive-by" but in git this is really
> irrelevant, I think.
>
>                              -David