[llvm-dev] [RFC] One or many git repositories?

Mehdi Amini via llvm-dev llvm-dev at lists.llvm.org
Sat Jul 30 11:28:57 PDT 2016

> On Jul 29, 2016, at 10:48 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote:
> On 29 Jul 2016, at 18:01, Mehdi Amini <mehdi.amini at apple.com> wrote:
>> I don’t understand this statement. As of today you can send a diff to the mailing list, I don’t see how lower the bar can be.
> Really?  You don’t see that hitting the web UI buttons that construct a pull request are lower than finding a mailing list to post to, subscribing, preparing a patch, emailing it, filtering out the firehose of unrelated things?  I migrated another open source project to GitHub last year.  After several years of accepting patches via a mailing list and receiving no patches as a result, I immediately started getting patches sent as pull requests.  I simply cannot overstate how much easier this mechanism is for downstream users to push fixes back, as long as the repo that they clone is the one that accepts pull requests.

Sure, I used Github in the past, and even set-up Jenkins bots that were testing pull-request before merge. However changing the upstream LLVM workflow has been deemed for future discussions, and I believe this is part of it. I.e. even if we move to github, using pull-request is not a given.


More information about the llvm-dev mailing list