all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com>
To: "František Kučera" <konference@frantovo.cz>, guix-devel@gnu.org
Subject: Re: moderation, please
Date: Sat, 12 Oct 2019 17:31:22 -0600	[thread overview]
Message-ID: <21a5a13b108fa1a3da604fdd3335c31d639ad410.camel@gmail.com> (raw)
In-Reply-To: <f0483287-8a2d-4f76-572d-75e43c4e7058@frantovo.cz>

On Sun, 2019-10-13 at 00:32 +0200, František Kučera wrote:
> Dne 13. 10. 19 v 0:16 Jesse Gibbons napsal(a):
> > When all 50+ new messages in this list from the past hour are off-topic, 
> > it
> > is too much.
> 
> 1) That statement is still present on the official Guix blog and thus
> this discussion is relevant.
> 
> 2) I honestly can not imagine how any mailing list could be useful in a
> e-mail client without thread support and filtering. So I expect that you
> use such client (and according to the MIME headers you use Evolution, so
> you are fine). And then: marking the whole thread with 50 messages as
> read is the same effort as marking a single message as read.
> 
> Franta


Evolution has a filter feature that doesn't work like it should, otherwise
the entire thread would have automatically been marked as read and moved to
a junk folder after I added the filter rule on Wednesday.

When I see 50 new unread mail from this mailing list, I think it is
reasonable to hope at least one of them is about developing guix.

  reply	other threads:[~2019-10-12 23:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-12 18:00 moderation, please ng0
2019-10-12 21:04 ` Dmitry Alexandrov
2019-10-12 22:16   ` Jesse Gibbons
2019-10-12 22:32     ` František Kučera
2019-10-12 23:31       ` Jesse Gibbons [this message]
2019-10-13 11:22         ` Enough Ricardo Wurmus
2019-10-13 11:12     ` moderation, please Dmitry Alexandrov
2019-10-13 10:27 ` ng0

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=21a5a13b108fa1a3da604fdd3335c31d639ad410.camel@gmail.com \
    --to=jgibbons2357@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=konference@frantovo.cz \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

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.