On Sat, May 6, 2017 at 10:50 PM, Eric Wong <e...@80x24.org> wrote: > (I have no idea what Jonathan Tirado wrote; it was encrypted (but > sent to a public list). > > Samuel Lijin <sxli...@gmail.com> wrote: >> Yep, I see these on public-inbox.org/git/ but not in my gmail inbox: > > Hi Samuel, check your Spam box (and move it to a normal inbox so > they can train it). Gmail filters are known to trigger happy > and incorrectly flag messages. It's been a problem on LKML, > too. > >> - Brandon [RFC 01/14] through [RFC 14/14] convert dir.c to take an >> index parameter > > Ironically, Brandon is a Google employee and Gmail seems to not > like his messages. The only flag I see from SpamAssassin in > public-inbox is HEADER_FROM_DIFFERENT_DOMAINS which happens to > every message because it's relayed via kernel.org > > Maybe Brandon can escalate this internally in Google... > > (OTOH, I noticed a thread/mbox download bug in public-inbox, > https://public-inbox.org/git/xmqqmvaq702u....@gitster.mtv.corp.google.com/t.mbox.gz > only shows two messages out of many. Will need to fix that...) > >> - Johanne's Coverity patch series > > Likewise, but he also uses freemail domain (nothing wrong with > that, but it raises one flag on SA). I noticed at least one > of his did trigger the RCVD_IN_SORBS_SPAM in SpamAssassin, but that's > a common problem with all freemail providers (including Gmail). > > > Anyways, I'm glad the SpamAssassin seems to be working well on > public-inbox and would be grateful to know if there's false > positives and missing messages. > > One of the major reasons I started public-inbox was because I > lack faith in my ability to run my little list server (with > mlmmj or mailman) and be able to successfully relay to the big > providers. Anyways, I'm glad it's helping readers of git@vger, > too :)
Thanks a lot for public-inbox, my only problem with it is that it doesn't cover every single mailing list I'm on, just git :) Are you or someone else maintaining some ancillary scripts for it? I probably need to fix my patch workflow but my usual mode is browsing in GMail & then manually 'git am'-ing some file I find with git-log commands. I have one to git am a patch from a msgid, thought I should write something to handle a series in some DWIM fashion (e.g. apply the latest continuous sequence of patches matching --author) but figured that someone's probably wrote this already & I don't need to hack it up myself...
