[llvm-dev] Add more projects into Git monorepo

[Mehdi AMINI via llvm-dev]

2017-05-09 9:03 GMT-07:00 David Chisnall <David.Chisnall at cl.cam.ac.uk>:

> On 9 May 2017, at 16:59, Mehdi AMINI <joker.eph at gmail.com> wrote:
> >
> > I'm not sure if you really read the last sentence of what I wrote, or if
> you followed the previous discussions on the plan here?
> > At this point I believe that this concern is non-existent per the
> read-only individual repo.
>
> The read-only repo is only useful if you don’t intend to contribute stuff
> back upstream.


Your point was about CI...
(unless you're working on some CI that would fix bugs and send PR?)


> There is no convenient workflow for cloning libunwind / libc++ /
> libwhatever, hacking on it, and sending pull requests.
>

We considered git-svn for this though.



>
> > We can leave it there :)
> > There have been extensive discussions, a BoF, and documentations, please
> refer you to these first (granted we haven't really talked about libunwind,
> but I'm not sure many people will be strongly opposed to libunwind having
> its separate life).
>
> There have been multiple discussions, and the conclusion from all that I
> have participated in was that projects that are tightly version locked to
> LLVM should be in the monorepo, everything else should be separate.
> Apparently there is now a plan underway to not do this and to make life
> harder for people who work on the projects that are not version locked to
> LLVM.
>

We have a different understanding.

-- 
Mehdi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170509/0dcd4841/attachment.html>