Guix-commits digest settings

  • Done
  • quality assurance status badge
Details
2 participants
  • Christopher Howard
  • Ludovic Courtès
Owner
unassigned
Submitted by
Christopher Howard
Severity
normal

Debbugs page

C
C
Christopher Howard wrote on 20 Jan 2020 12:53
(address . bug-guix@gnu.org)
71ad7f649a3f7a13b8e18e57bceb3a8333d7fb54.camel@alaskasi.com
Hello, would it be possible for the Guix-commits list administrator to
tune the Digest settings, so as to reduce the numbers of Digest emails
sent each day? I'm using Digest mode, but still receive about 8-15
emails per day. One thing that might help is to increase the number of
messages that can be lumped into one digest: I frequently receive two
or three emails within 30 seconds of each other, than have nine
messages in each. I think you can adjust also how long the system waits
before creating a new digest.


--
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: file
L
L
Ludovic Courtès wrote on 27 Jan 2020 13:49
(name . Christopher Howard)(address . christopher@alaskasi.com)(address . 39209@debbugs.gnu.org)
87k15cfu3m.fsf@gnu.org
Hi Christopher,

Christopher Howard <christopher@alaskasi.com> skribis:

Toggle quote (9 lines)
> Hello, would it be possible for the Guix-commits list administrator to
> tune the Digest settings, so as to reduce the numbers of Digest emails
> sent each day? I'm using Digest mode, but still receive about 8-15
> emails per day. One thing that might help is to increase the number of
> messages that can be lumped into one digest: I frequently receive two
> or three emails within 30 seconds of each other, than have nine
> messages in each. I think you can adjust also how long the system waits
> before creating a new digest.

I’ve changed ‘digest_size_threshold’ from 30 to 300 KB. This option is
documented 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’.
L
L
Ludovic Courtès wrote on 27 Jan 2020 13:49
control message for bug #39209
(address . control@debbugs.gnu.org)
87imkwfu3f.fsf@gnu.org
tags 39209 fixed
close 39209
quit
C
C
Christopher Howard wrote on 28 Jan 2020 10:42
Re: bug#39209: Guix-commits digest settings
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 39209@debbugs.gnu.org)
16060669582e0029c8b16afa5b4f4efee1fce29a.camel@alaskasi.com
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: file
?
Your comment

This issue is archived.

To comment on this conversation send an email to 39209@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 39209
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch