public inbox for git@vger.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: Thu, 29 May 2014 21:23:06 +0200	[thread overview]
Message-ID: <87tx88fkyt.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20140529185311.GB10865@sigill.intra.peff.net> (Jeff King's message of "Thu, 29 May 2014 14:53:11 -0400")

Jeff King <peff@peff•net> writes:

> 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.
>
> I do not think Junio or anyone else has the technical ability to remove
> messages from the archive.

You can post self-destructing messages by adding X-no-archive: yes if I
am not mistaken.  But that only concerns stuff you post yourself.

> There is not one archive, but rather several that get messages
> straight from vger.kernel.org and keep their own database (e.g.,
> gmane, marc, spinics, nabble).

Frankly, I find it weird that vger.kernel.org does not have an archive
of its own.  But yes, that makes it unlikely that silent censorship is
much of a thing.  A list moderator may put a particular sender on silent
moderation, where postings will only appear once he has acknowledged
them.  However, that is a manual and burdensome process and requires an
up-front decision to do so.  Once a message made it to the list, the
various archives will pick it up.

-- 
David Kastrup

  reply	other threads:[~2014-05-29 19:23 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 [this message]
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
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=87tx88fkyt.fsf@fencepost.gnu.org \
    --to=dak@gnu$(echo .)org \
    --cc=felipe.contreras@gmail$(echo .)com \
    --cc=git-fc@googlegroups$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=peff@peff$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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