aaron.ballman added a comment.

In D146530#4213076 <https://reviews.llvm.org/D146530#4213076>, @ipriyanshi1708 
wrote:

> In D146530#4213045 <https://reviews.llvm.org/D146530#4213045>, @aaron.ballman 
> wrote:
>
>> This appears to be the same efforts that have been going on in 
>> https://reviews.llvm.org/D146041. Can you coordinate with @AryanGodara so 
>> that there's only one patch for this?
>
> Hi! I am an Outreachy applicant, firstly how can I coordinate with 
> @AryanGodara and secondly how will it be counted as my contribution and then 
> can I record it in my final application? Or I will have to look for some 
> other issues for Outreachy?

Welcome! You can comment on the other review to see if the author would like to 
collaborate with you on a solution. We have the ability to land commits with 
co-author tags (please request it explicitly when someone approves the patch so 
that the person landing the work knows to do this), so that should get you both 
the attribution in GitHub that you did the work (no idea if Outreachy has rules 
around co-authoring though). You might have to look for other issues for 
Outreachy, depending on what they require.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D146530/new/

https://reviews.llvm.org/D146530

_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to