[llvm-dev] Phabricator projects/subprojects (& opaque pointer work)
Arthur Eubanks via llvm-dev
llvm-dev at lists.llvm.org
Tue Jun 22 08:23:40 PDT 2021
Yup, will do. Thanks for doing this, this makes a lot of sense!
On Tue, Jun 22, 2021 at 12:10 AM David Blaikie <dblaikie at gmail.com> wrote:
> Thanks!
>
> Arthur - could you make sure any reviews you're doing or sending are
> tagged with this project?
>
> On Mon, Jun 21, 2021 at 9:55 PM Mehdi AMINI <joker.eph at gmail.com> wrote:
>
>>
>>
>> On Mon, Jun 21, 2021 at 9:45 PM David Blaikie <dblaikie at gmail.com> wrote:
>>
>>> fair enough - figured I'd check, but yeah, no big deal either way. Maybe
>>> they'd offer some more chance to help scale up review as the project grows
>>> and we all drown a bit under the mass of email to -commits lists. Though
>>> requiring people to manually attribute reviews with projects/etc is
>>> probably not going to work very reliably.
>>>
>>> Would you mind creating one for opaque pointers? Perhaps
>>> "opaque-pointers" would be a good name? At least myself and Arthur should
>>> be members I think.
>>>
>>
>> Here you go: https://reviews.llvm.org/project/view/106/
>>
>>
>>>
>>> On Mon, Jun 21, 2021 at 9:26 PM Mehdi AMINI <joker.eph at gmail.com> wrote:
>>>
>>>> Hey David,
>>>>
>>>> I think it used to be that anyone could create these, and then we got
>>>> some unfortunate events where someone would just mess everything up on Phab
>>>> and we restricted it.
>>>> I'm open to going back to the "free for all" model, but at the same
>>>> time it seems that creating projects/subprojects isn't a frequent need
>>>> either: I've been happy to create them on demand as well for the last year.
>>>>
>>>> Cheers,
>>>>
>>>> --
>>>> Mehdi
>>>>
>>>> On Mon, Jun 21, 2021 at 6:21 PM David Blaikie <dblaikie at gmail.com>
>>>> wrote:
>>>>
>>>>> Hey Mehdi,
>>>>>
>>>>> In your capacity as Phabricator admin - I'm wondering what thoughts
>>>>> you have on Phabricator projects or subprojects. Currently it looks like
>>>>> they can only be made by certain administrators, but I'm wondering if it'd
>>>>> make sense to allow more folks to make at least subprojects of LLVM for
>>>>> tracking certain work? I'd specifically like to create a subproject for the
>>>>> opaque pointer work to make it clearer all the patches going into
>>>>> that/easier to track it/etc - but also wondering about the more general
>>>>> issue of project/subproject creation permissions, etc.
>>>>>
>>>>> (I see currently the Phab LLVM project has no subprojects - instead
>>>>> other top level projects exist (I'm a member of the "debug-info" subproject
>>>>> and "clang-modules" subprojects, which I guess needed some admin to create
>>>>> them but then arbitrary folks could join them after that) - should they be
>>>>> subprojects of LLVM instead? I guess it probably doesn't matter greatly at
>>>>> the moment, but if we allowed more free access to create them, maybe we'd
>>>>> want more hierarchy)
>>>>>
>>>>> - Dave
>>>>>
>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210622/30d1f871/attachment.html>
More information about the llvm-dev
mailing list