user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Eric Wong <e@80x24.org>
Cc: Samuel Lijin <sxlijin@gmail.com>,
	Jonathan Tirado <tiradojonathan32@gmail.com>,
	 Jeff King <peff@peff.net>,
	Git Mailing List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>,
	 Brandon Williams <bmwill@google.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	meta@public-inbox.org
Subject: Re: vger not relaying some of Junio's messages today?
Date: Sat, 6 May 2017 23:05:54 +0200	[thread overview]
Message-ID: <CACBZZX42rhmrq8z0u1aRXw87oT22YywwnaFHUMjDYgtE_i56nw@mail.gmail.com> (raw)
In-Reply-To: <20170506205041.GA26189@starla>

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 <sxlijin@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.fsf@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...

  reply	other threads:[~2017-05-06 21:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <v26esrmyqyqykypjs75fx2vy.1494092763967@email.android.com>
     [not found] ` <CAJZjrdWYDMFHRrbeFk89p+GebLpWJBUQfnpC6w87aVh8czL5_w@mail.gmail.com>
2017-05-06 20:50   ` vger not relaying some of Junio's messages today? Eric Wong
2017-05-06 21:05     ` Ævar Arnfjörð Bjarmason [this message]
2017-05-06 21:42       ` Eric Wong
2017-05-08 10:42       ` Johannes Schindelin
2017-05-08 17:01         ` Brandon Williams
2017-05-09 10:10           ` Johannes Schindelin
2017-05-06 21:10     ` Samuel Lijin
2017-05-07  0:26       ` Eric Wong
2017-05-08 17:05         ` Brandon Williams
2017-05-07  1:05       ` Eric Wong
2017-05-07  3:00         ` Junio C Hamano
2017-05-07  3:24           ` Eric Wong
2017-05-07 12:41     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACBZZX42rhmrq8z0u1aRXw87oT22YywwnaFHUMjDYgtE_i56nw@mail.gmail.com \
    --to=avarab@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=bmwill@google.com \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=meta@public-inbox.org \
    --cc=peff@peff.net \
    --cc=sxlijin@gmail.com \
    --cc=tiradojonathan32@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).