All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, git-fc@googlegroups.com
Subject: Re: [ANNOUNCE] Git v2.0.0
Date: Sat, 31 May 2014 11:52:24 +0200	[thread overview]
Message-ID: <87k392e0mf.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <5388fb283edaf_bd8167d3002b@nysa.notmuch> (Felipe Contreras's message of "Fri, 30 May 2014 16:42:00 -0500")

Felipe Contreras <felipe.contreras@gmail.com> writes:

> Jeff King wrote:
>> On Wed, May 28, 2014 at 06:17:25PM -0500, Felipe Contreras wrote:
>> 
>> > This is the last mail I sent to you, because you ignore them anyway, and
>> > remove them from the mailing list.
>> > [...]
>> > [2], a mail you conveniently removed from the tracked record.
>> > [...]
>> > You also conveniently removed this mail from the archives.
>> 
>> I see you already noticed the changes in v2.0, but I wanted to address
>> these points, because I consider silent censorship to be a serious
>> accusation.
>
> Yes, I also think silent censorship is a very seriours matter, and I was
> very dissapointed that this mailing list would engage in that.
>
>> I've reported the bug to gmane.discuss (no link yet, as I'm waiting
>> for the message to go through, but it is not a high traffic group, so
>> it should be easy to find the thread once it is there).
>
> Thanks. At first I thought that was the reason, but then I noticed it
> was always my mails that seemed to get this "bug", so I decided it was
> too much of a coincidence.

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.

So there may a bias against long-running threads with multiple
participants with regard to timely delivery.

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.

-- 
David Kastrup

  reply	other threads:[~2014-05-31  9:52 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 [this message]
2014-06-02  6:36         ` Jeff King
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=87k392e0mf.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.