From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 4 19:26:12 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 690BB4D6; Wed, 4 Jun 2014 19:26:12 +0000 (UTC) Received: from icp-osb-irony-out1.external.iinet.net.au (icp-osb-irony-out1.external.iinet.net.au [203.59.1.210]) by mx1.freebsd.org (Postfix) with ESMTP id ACFD026E9; Wed, 4 Jun 2014 19:26:10 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgMUAORxj1N90YHN/2dsb2JhbABZgwdSg0SKN50fAQEBAQEGmCcBgRAWdIIlAQEEASMPAUYFCwsNCgECAgUhAgIPBRgjDhOIOgcOrAmlaheBKoQriH0HgnU2gRUEmhKGWkCMIINKKw X-IronPort-AV: E=Sophos;i="4.98,974,1392134400"; d="scan'208";a="230043259" Received: from unknown (HELO smtp.phoenix) ([125.209.129.205]) by icp-osb-irony-out1.iinet.net.au with ESMTP; 05 Jun 2014 03:26:03 +0800 Received: by smtp.phoenix (Postfix, from userid 1001) id B8BDC694; Thu, 5 Jun 2014 05:26:02 +1000 (EST) Date: Thu, 5 Jun 2014 05:26:02 +1000 From: andrew clarke To: Jonathan Anderson Subject: Re: There is currently no usable release of FreeBSD. Message-ID: <20140604192602.GA54953@ozzmosis.com> References: <332D72DF-2225-40E2-B246-0786181AAB51@tony.li> <538F5FB5.9060008@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <538F5FB5.9060008@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-hackers@freebsd.org, Tony Li X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 19:26:12 -0000 On Wed 2014-06-04 15:34:37 UTC-0230, Jonathan Anderson (jonathan@FreeBSD.org) wrote: > Tony Li wrote: > > What’s the problem with using ‘legacy’? > > Is the problem actually that we're using the term "legacy", which some > vendors use to mean "unsupported"? Perhaps we ought to say: The Subject: line is trollbait but I think at the very least "legacy" is a confusing term to use, with unneccessarily (in this instance) negative connotations for what is after all very good, reliable, supported, software. http://en.wikipedia.org/wiki/Legacy_system http://en.wikipedia.org/wiki/Legacy_code Merely a documentation issue, not a code quality/@hackers issue. Regards Andrew