From owner-ctm-users@freebsd.org Wed Aug 19 16:41:28 2015 Return-Path: Delivered-To: ctm-users@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02C3E9BE192 for ; Wed, 19 Aug 2015 16:41:28 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A14B1F7A for ; Wed, 19 Aug 2015 16:41:26 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p5083C60E.dip0.t-ipconnect.de [80.131.198.14]) (authenticated bits=128) by slim.berklix.org (8.14.5/8.14.5) with ESMTP id t7JFpI8G001911; Wed, 19 Aug 2015 17:51:19 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id t7JFmGa3046800; Wed, 19 Aug 2015 17:48:16 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id t7JFljKD051122; Wed, 19 Aug 2015 17:48:03 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201508191548.t7JFljKD051122@fire.js.berklix.net> To: stephen@missouri.edu, ctm-users@freebsd.org Subject: Re: Do you still need CTM? From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Thu, 20 Aug 2015 00:14:04 +0900." <20150820.001404.104049290.kaminaga@nat.gunma-ct.ac.jp> Date: Wed, 19 Aug 2015 17:47:45 +0200 X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2015 16:41:28 -0000 I am Against killing CTM. (I was drafting reply when my X11 crashed so proper reply in a bit.) Cheers, Julian -- Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich http://berklix.com Reply after previous text, like a play - Not before, which looses context. Indent previous text with "> " Insert new lines before 80 chars. Send plain text, Not quoted-printable, Not HTML, Not ms.doc, Not base64. Subsidise contraception V. Global warming, pollution, famine, migration.