emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins <jamshark70@gmail.com>
To: Bastien <bzg@altern.org>
Cc: jamshark70@dewdrop-world.net, emacs-orgmode@gnu.org
Subject: Re: Digest configuration
Date: Wed, 19 Sep 2012 08:29:50 +0800	[thread overview]
Message-ID: <CAFniQ7U7Hw7uXMZvkBWRsVR-hi=w8cB5aOdd=N-DtYPQ2EHxhQ@mail.gmail.com> (raw)
In-Reply-To: <87obl38w5e.fsf@bzg.ath.cx>

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

On Sep 18, 2012 6:26 PM, "Bastien" <bzg@altern.org> wrote:
>
> Hi James,
>
> James Harkins <jamshark70@gmail.com> writes:
>
> > There must be a smarter way to group messages into digests so that no
> > single digest is too big, while messages don't get lost.
>
> I assume this is about mailman digests.
>
> If so, please report this to the mailman developers.
>
> We don't have any way to fix this from here.

I'm also subscribed to the lilypond-users list, also hosted at gnu.org, and
its digests have the same format, so I assume it's also mailman.
Lilypond-users, however, delivers several digests per day and there seems
to be a size cap on each one. If there are more posts in a day, I get more
digests, not one longer digest.

So I suppose the maximum digest size is already configurable without
logging an issue with the mailman devs.

hjh

[-- Attachment #2: Type: text/html, Size: 1139 bytes --]

  reply	other threads:[~2012-09-19  0:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFniQ7Wn-CJy6OxLO5u2+-BUpp+oCY1=s81U0XxFpFE1QXVRKg@mail.gmail.com>
     [not found] ` <CAFniQ7Uucvkj=k1YUy9cqcxqxys=_scSOgKmHqXQmdYaWBtYhw@mail.gmail.com>
2012-09-13 12:09   ` Digest configuration James Harkins
2012-09-18  6:56     ` Bastien
2012-09-19  0:29       ` James Harkins [this message]
2012-09-19  6:23         ` Bastien
2012-09-19 18:41           ` Achim Gratz
2012-09-21  8:55             ` Bastien

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://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFniQ7U7Hw7uXMZvkBWRsVR-hi=w8cB5aOdd=N-DtYPQ2EHxhQ@mail.gmail.com' \
    --to=jamshark70@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jamshark70@dewdrop-world.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).