[LLVMdev] gmail marking llvm emails as spam? Re:

Yaron Keren yaron.keren at gmail.com
Mon May 12 13:04:04 PDT 2014


I have seen few messages in spam and the lists asked me to re-confirm
subscription due to excessive bounces.



2014-05-12 21:52 GMT+03:00 Robinson, Paul <
Paul_Robinson at playstation.sony.com>:

>  I wonder if gmail is having other issues. I read the lists from a gmail
> account; lately I've seen a few messages that were flagged as containing
> "suspicious" code, and both llvm-commits and cfe-commits have complained to
> me about excessive bounces in the past week.
>
> --paulr
>
>
>
> *From:* llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] *On
> Behalf Of *Sean Silva
> *Sent:* Monday, May 12, 2014 11:14 AM
> *To:* Carter Schonwald
> *Cc:* LLVM Developers Mailing List
> *Subject:* Re: [LLVMdev] gmail marking llvm emails as spam? Re:
>
>
>
> You can set up a gmail filter selecting mailing list emails and select
> "never mark as spam".
>
>
>
> -- Sean Silva
>
>
>
> On Mon, May 12, 2014 at 10:43 AM, Carter Schonwald <
> carter.schonwald at gmail.com> wrote:
>
> i Don't know if others have raised this issue, but I'm seeing *a lot* of
> llvm-dev emails and cfe emails landing in my spam folder in gmail. Are
> other people having this problem?
>
>
>
> On Mon, May 12, 2014 at 11:57 AM, Tom Stellard <tom at stellard.net> wrote:
>
> Hi,
>
> I would like to begin the 3.4.2 release process for LLVM.  There have
> been two issues identified in 3.4.1, which there is interest in having
> fixed in a 3.4.x release:
>
> 1. Build failure with gcc 4.9 (This is not a regression, 3.4 also fails
> to build with gcc 4.9).
>
> 2. Accidental change of libLLVM's DT_SONAME  from libLLVM-3.4
> libLLVM-3.4.1.so
>
> I will also accept any other bug-fixes that people want to submit as
> long as they conform to the rules of stable releases:
> http://llvm.org/docs/HowToReleaseLLVM.html#release-patch-rules
>
> In order to get these fixes out quickly, we will have a very short period
> for nominating bug-fixes, followed by our usually stable release testing
> phase.
>
> Here is an approximate schedule:
>
> Monday, May 12 to Thursday, May 15: Nominate bug-fixes for the 3.4 branch.
> Friday, May 16 to Friday, May 23:   Testing Phase I
> Monday, May 25:                     Release or Phase II of testing if
> necessary.
>
> If you are interested in helping with release qualification testing
> of  3.4.2, send me an email with the target, operating system and host
> compiler you can test with.  Since we have fixes specifically for gcc
> 4.9 in this release we need some testers who can test with gcc 4.9.
>
> Besides release qualification, it will be helpful to have people building
> the 3.4 branch with gcc 4.9 and looking for potential issues.  This can be
> done before the testing phase once the gcc 4.9 fixes have landed.
>
> I have a busy schedule in the next month, so I would like to have one or
> more
> backup up release managers, in case I am unable to make this release in a
> timely
> manner.  If you are interested in this, let me know.
>
> Thanks,
> Tom
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140512/6ad9a641/attachment.html>


More information about the llvm-dev mailing list