From: Ken Rose <kenrose@nc-sys.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Book sales
Date: Wed, 23 May 2007 09:22:12 -0700 [thread overview]
Message-ID: <46546A34.9080505@nc-sys.com> (raw)
In-Reply-To: <20070523002052.GA463@first.in-berlin.de>
Oliver Bandel wrote:
> For my taste you too often mention your book here in this list....
> it's ok, if you tell it once or twice, but this is not your personal
> advertising channel.
OK, so I had some time to kill this morning...
I counted 123 posts from Jon this year so far. In those, not counting
his .signature (which is, as protocol demands, not more than 4 lines
long), he mentioned his book in 8. Some of those are replies to posts
that essentially ask for pointers to books. A few are more blatantly
self-serving, but even so, it doesn't seem excessive to me.
- ken
next prev parent reply other threads:[~2007-05-23 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 23:54 Jon Harrop
2007-05-23 0:20 ` [Caml-list] " Oliver Bandel
2007-05-23 4:47 ` Paul Snively
2007-05-23 9:21 ` Oliver Bandel
2007-05-23 15:01 ` lloyd
2007-05-23 16:14 ` skaller
2007-05-23 16:22 ` Ken Rose [this message]
[not found] ` <200705230141.10109.jon@ffconsultancy.com>
2007-05-23 22:08 ` Oliver Bandel
2007-05-24 0:25 ` Jacques Garrigue
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=46546A34.9080505@nc-sys.com \
--to=kenrose@nc-sys.com \
--cc=caml-list@inria.fr \
--cc=rose@acm.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