From: Jeff King <peff@peff.net>
To: David Kastrup <dak@gnu.org>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, git-fc@googlegroups.com
Subject: Re: [ANNOUNCE] Git v2.0.0
Date: Mon, 2 Jun 2014 02:36:07 -0400 [thread overview]
Message-ID: <20140602063607.GA27445@sigill.intra.peff.net> (raw)
In-Reply-To: <87k392e0mf.fsf@fencepost.gnu.org>
On Sat, May 31, 2014 at 11:52:24AM +0200, David Kastrup wrote:
> Some mailing list filters and/or spam filters flag mails with too many
> recipients so that they need to pass through moderation first. The
> typical threads on this list are short and have few recipients while
> longer threads, due to the list policy of adding every participants to
> the Cc, will tend to have more recipients.
AFAIK, vger does not do anything like this. They block HTML, messages
lacking a message-id, messages over 100K, and certain taboo phrases:
http://vger.kernel.org/majordomo-info.html#taboo
And anyway, I do not think vger is responsible here. The messages were
delivered through the list, and other archives have them. This looks
like a gmane problem.
According to gmane.org, their admins will look manually at messages
flagged as spam, but I find it unlikely that they flagged several days
worth of git traffic (and when they do, I think they cross-post them to
a spam group in NNTP, and the messages do not seem to be marked as
such). So I think this really is just a bug.
> And frankly, if I were a list moderator and software asked me through
> this sort of coincidence whether a mail should be delivered or not and a
> glance at it shows nothing but insults, wild accusations, threats and so
> on for the umpteenth time, I'd consider twice clicking "Accept".
> Whether or not I ultimately did so, this would likely contribute to the
> delay.
I do not disagree, but please let's not rehash all of that again.
-Peff
next prev parent reply other threads:[~2014-06-02 6:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 22:31 [ANNOUNCE] Git v2.0.0 Junio C Hamano
2014-05-28 22:43 ` Junio C Hamano
2014-05-28 23:17 ` Felipe Contreras
2014-05-28 23:42 ` Felipe Contreras
2014-05-29 18:53 ` Jeff King
2014-05-29 19:23 ` David Kastrup
2014-05-29 19:45 ` Jeff King
2014-05-30 21:42 ` Felipe Contreras
2014-05-31 9:52 ` David Kastrup
2014-06-02 6:36 ` Jeff King [this message]
2014-06-02 6:57 ` Felipe Contreras
2014-06-02 7:24 ` David Kastrup
2014-06-03 2:08 ` NeilBrown
2014-06-03 2:59 ` Linus Torvalds
2014-06-03 11:46 ` NeilBrown
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140602063607.GA27445@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dak@gnu.org \
--cc=felipe.contreras@gmail.com \
--cc=git-fc@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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 NNTP newsgroup(s).