[llvm-dev] New LLVM git repository conversion prototype

[James Y Knight via llvm-dev]

The change to move dragonegg, poolalloc, and safecode into "archive" has
been made, and the repository set regenerated. (Which of course means all
the commit hashes have changed -- that's why this is still marked
"prototype"!)

You will need to re-clone (from the same URLs:
https://github.com/llvm-git-prototype/)

On Thu, Oct 18, 2018 at 8:24 AM James Y Knight <jyknight at google.com> wrote:

>
>
> On Thu, Oct 18, 2018 at 1:29 AM Chandler Carruth <chandlerc at gmail.com>
> wrote:
>
>> I was doing my sanity checking. First, I was focused on the projects.
>> Some notes below:
>>
>> On Thu, Oct 11, 2018 at 3:28 PM James Y Knight via llvm-dev <
>> llvm-dev at lists.llvm.org> wrote:
>>
>>>   * dragonegg (also "gcc-plugin", the original name)
>>>
>>
>> As discussed at the round table, I would suggest migrating both of these
>> into the "archive" repo below.
>>
>
> SGTM. Last modification was 2014. Seems dead. I could also separate it out
> into a separate dragonegg repo, if someone wants to actually work on it as
> a separate project. (There was some interest expressed in continuing
> development a while back, I think? But I guess it didn't go anywhere).
> Lacking such a request, into archive seems good.
>
>  A couple inactive projects which are somewhat related to the LLVM
>> codebase, migrated to separate repos:
>>
>   * poolalloc
>>>   * safecode
>>>
>>
>> Since these are inactive, could we move these into the "archive" repo as
>> well? That would clean up the top-level stuff I think.
>>
>
> SGTM. I had originally split them off because I thought they might be
> viable independent projects, even though we wanted them not to be part of
> the llvm repository. When we first started discussing this whole git
> migration thing, those projects had actually been active not _that_ long
> ago. But, it's now been a while, and they show no signs of anyone wanting
> to continue them. If anyone actually does want to pick it up 10 years in
> the future, they can certainly pull it out of there without much fuss. :)
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181018/b006dd28/attachment.html>