From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Your message to Ksummit-discuss awaits moderator approval
Date: Sat, 03 May 2014 20:35:47 +0200 [thread overview]
Message-ID: <53653703.4010407@gmail.com> (raw)
In-Reply-To: <20140503155156.GA11659@thunk.org>
On 05/03/2014 05:51 PM, Theodore Ts'o wrote:
> On Sat, May 03, 2014 at 05:00:14PM +0200, Michael Kerrisk (man-pages) wrote:
>> Can we get this limit lifted? Otherwise, we have to play silly games working out
>> who (and how many) to trim from CC, or live with delayed messages to the list...
>
> I've bumped it to 50, which hopefully should be enough.
Thanks, Ted.
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2014-05-03 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1841.1399124228.1428.ksummit-discuss@lists.linuxfoundation.org>
2014-05-03 15:00 ` Michael Kerrisk (man-pages)
2014-05-03 15:51 ` Theodore Ts'o
2014-05-03 18:35 ` Michael Kerrisk (man-pages) [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53653703.4010407@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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