[llvm-dev] [cfe-dev] IMPORTANT: LLVM Bugzilla migration

chuanqi.xcq via llvm-dev llvm-dev at lists.llvm.org
Thu Nov 25 23:33:12 PST 2021


Got it. My bad to ignore the Q&A. And I thought it is a little bit fast. I recevied it in Nov 23 and the dead line was Nov 24. 
Luckily, it might not be big problem for me since my issues are not so many. I think I could subscribe the corresponding issue by hand after the migration.

Thanks,
Chuanqi
------------------------------------------------------------------
From:Anton Korobeynikov <anton at korobeynikov.info>
Send Time:2021年11月26日(星期五) 15:22
To:chuanqi.xcq <yedeng.yd at linux.alibaba.com>
Cc:llvm-dev <llvm-dev at lists.llvm.org>; clang developer list <cfe-dev at lists.llvm.org>
Subject:Re: [cfe-dev] [llvm-dev] IMPORTANT: LLVM Bugzilla migration

Hello

The email you received (as well as several other email notifications
sent over last 6 months) already contains the relevant answer:

   Q: What will happen if I will not provide email - username mapping?
   A: All data produced by unidentified users will be anonymized
during the migration, so there will be no way to attribute data to a
particular github username

Hope this helps

On Fri, Nov 26, 2021 at 5:03 AM chuanqi.xcq via cfe-dev
<cfe-dev at lists.llvm.org> wrote:
>
> Sorry if my question is discussed before.
>
> I received a mail which requires me to offer a bugzilla/username mapping and the deadline was Nov 24.
>
> But I was out of work unluckily so I missed that one. So I want to ask if my previous issues would be missing? Or what should I do in this case?
>
> Thanks,
> Chuanqi
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev



-- 
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20211126/98390048/attachment.html>


More information about the llvm-dev mailing list