From: Christopher Howard <christopher@alaskasi.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 39209@debbugs.gnu.org
Subject: bug#39209: Guix-commits digest settings
Date: Tue, 28 Jan 2020 09:42:49 -0900 [thread overview]
Message-ID: <16060669582e0029c8b16afa5b4f4efee1fce29a.camel@alaskasi.com> (raw)
In-Reply-To: <87k15cfu3m.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]
Hi, yes, this looks like it had immediate benificial effect. It looks
like it is packing about five times as many commit messages into each
email, which has dramatically reduced the inbox clutter. Thank you!
-----Original Message-----
From: Ludovic Courtès <ludo@gnu.org>
To: Christopher Howard <christopher@alaskasi.com>
Cc: 39209@debbugs.gnu.org
Subject: Re: bug#39209: Guix-commits digest settings
Date: Mon, 27 Jan 2020 22:49:17 +0100
Hi Christopher,
Christopher Howard <christopher@alaskasi.com> skribis:
Hello, would it be possible for the Guix-commits list administrator
totune the Digest settings, so as to reduce the numbers of Digest
emailssent each day? I'm using Digest mode, but still receive about 8-
15emails per day. One thing that might help is to increase the number
ofmessages that can be lumped into one digest: I frequently receive
twoor three emails within 30 seconds of each other, than have
ninemessages in each. I think you can adjust also how long the system
waitsbefore creating a new digest.
I’ve changed ‘digest_size_threshold’ from 30 to 300 KB. This option
isdocumented like this:
digest_size_threshhold (digest): How big in Kb should a digest
be before it gets sent out? 0 implies no maximum size.
So I think it should be better now. Let me know!
Ludo’.
--
Christopher Howard
Enterprise Solutions Manager
Alaska Satellite Internet
PO Box 70, Ester, AK 99725
3239 La Ree Way, Fairbanks, AK 99709
907.451.0088
1.888.396.5623
www.alaskasatelliteinternet.com
[-- Attachment #2: Type: text/html, Size: 2553 bytes --]
prev parent reply other threads:[~2020-01-28 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 20:53 bug#39209: Guix-commits digest settings Christopher Howard
2020-01-27 21:49 ` Ludovic Courtès
2020-01-28 18:42 ` Christopher Howard [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16060669582e0029c8b16afa5b4f4efee1fce29a.camel@alaskasi.com \
--to=christopher@alaskasi.com \
--cc=39209@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).