Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Thomas Fischbacher <tf@functionality.de>
To: Vincent Hanquez <tab@snarc.org>
Cc: Caml-list List <caml-list@inria.fr>
Subject: Re: [Caml-list] Suggestion
Date: Wed, 30 Jan 2008 13:38:42 +0000	[thread overview]
Message-ID: <47A07DE2.3000404@functionality.de> (raw)
In-Reply-To: <20080130132544.GC3921@snarc.org>


Vincent Hanquez wrote:

>>Considering the noticeable increase in traffic on this list which does
>>not seem to be about to decline, may I suggest splitting it into
>>caml-impl (dealing with language implementation issues only) and
>>caml-list?
> 
> yes, it was so much better when that was dead (!)

Frankly, there is a lot of pointless noise on the list at present
that is of no interest at all to application-minded subscribers.

-- 
best regards,
Thomas Fischbacher
tf@functionality.de


  parent reply	other threads:[~2008-01-30 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30  2:01 Suggestion Thomas Fischbacher
2008-01-30 13:25 ` [Caml-list] Suggestion Vincent Hanquez
2008-01-30 13:30   ` Hugo Ferreira
2008-01-30 13:38   ` Thomas Fischbacher [this message]
2008-01-30 14:41     ` Peng Zang

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=47A07DE2.3000404@functionality.de \
    --to=tf@functionality.de \
    --cc=caml-list@inria.fr \
    --cc=tab@snarc.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