From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: regex overflow
Date: Fri, 16 Sep 2011 09:31:20 +0900 [thread overview]
Message-ID: <b4mobyl72g7.fsf@jpl.org> (raw)
In-Reply-To: <m3mxe5zd1d.fsf@jhcloos.com>
James Cloos wrote:
> A couple of today's posts on cairo-commits have *long* Subjects; one is
> 32726 and the other 58897 octets long.
> (It uses a subject format which includes the full list of files affected
> by the changeset.)
> Attempts to enter the group failed with a regex stack overflow error.
Could you provide a Lisp backtrace? I tried
http://lists.cairographics.org/archives/cairo-commit/2011-September.txt.gz
by using nndoc, and also nnml to which I copied articles from
the nndoc group. No problem.
next prev parent reply other threads:[~2011-09-16 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 21:54 James Cloos
2011-09-16 0:31 ` Katsumi Yamaoka [this message]
2011-09-16 14:51 ` James Cloos
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=b4mobyl72g7.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).