All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: Jeff King <peff@peff.net>
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, 02 Jun 2014 09:24:09 +0200	[thread overview]
Message-ID: <871tv7bwpy.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20140602063607.GA27445@sigill.intra.peff.net> (Jeff King's message of "Mon, 2 Jun 2014 02:36:07 -0400")

Jeff King <peff@peff.net> writes:

> 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.

I am reading more than one list through Gmane/nntp, and in the last
years it was not infrequent that delivery paused for even days and/or
spurious old messages from the last day or even more were getting
redelivered.

> 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.

Quite so.  In particular when other mirrors got the messages timely.

-- 
David Kastrup

  parent reply	other threads:[~2014-06-02  7:59 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
2014-06-02  6:57           ` Felipe Contreras
2014-06-02  7:24           ` David Kastrup [this message]
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=871tv7bwpy.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=felipe.contreras@gmail.com \
    --cc=git-fc@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.