From owner-freebsd-sparc64@freebsd.org  Tue Jul 10 21:06:15 2018
Return-Path: <owner-freebsd-sparc64@freebsd.org>
Delivered-To: freebsd-sparc64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C94ED102C311
 for <freebsd-sparc64@mailman.ysv.freebsd.org>;
 Tue, 10 Jul 2018 21:06:15 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id 6624A8C350
 for <freebsd-sparc64@freebsd.org>; Tue, 10 Jul 2018 21:06:15 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 1C9A6102C30B; Tue, 10 Jul 2018 21:06:15 +0000 (UTC)
Delivered-To: sparc64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0874F102C308
 for <sparc64@mailman.ysv.freebsd.org>; Tue, 10 Jul 2018 21:06:15 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mail.soaustin.net",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id A92BB8C34D
 for <sparc64@freebsd.org>; Tue, 10 Jul 2018 21:06:14 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: from lonesome.com (unknown [18.188.142.31])
 by mail.soaustin.net (Postfix) with ESMTPSA id AF62C24936;
 Tue, 10 Jul 2018 21:06:13 +0000 (UTC)
Date: Tue, 10 Jul 2018 21:06:12 +0000
From: Mark Linimon <linimon@lonesome.com>
To: Joshua Pincus <joshua.pincus@gmail.com>
Cc: Craig Butler <craig001@lerwick.hopto.org>, sparc64@freebsd.org
Subject: Re: sparc64 for the bin ??
Message-ID: <20180710210611.GA13112@lonesome.com>
References: <6d8e7041b2a93b6dfc5823b13b27308b5c27f005.camel@lerwick.hopto.org>
 <20180710202204.GA11015@lonesome.com>
 <CAEO4AA7YwA0iyv9svKDRYRkLqNuXjvrRsdfqyb-2zn-HYQpxNA@mail.gmail.com>
 <20180710203705.GA11940@lonesome.com>
 <CAEO4AA6h3i6jfEiNcw1FyjEnKneij9=cnYT+SViNRrRGRHoGRw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAEO4AA6h3i6jfEiNcw1FyjEnKneij9=cnYT+SViNRrRGRHoGRw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-sparc64>, 
 <mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64/>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>, 
 <mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2018 21:06:16 -0000

On Tue, Jul 10, 2018 at 04:43:17PM -0400, Joshua Pincus wrote:
> Is there no way to leave it as an unsupported arch of some kind?

Per the official support page, stable/11 will be supported through
September 30, 2021.  So even if sparc64 src is deleted from 12, it
will still be usable on 11 through that time:

  https://www.freebsd.org/security/security.html#sup

I suppose we could try to convince the src people to leave it in the
tree for 12, but merely disconnected; however, I think once it's
disconnected it will just bitrot.  That was certainly the fate of
the alpha arch.  (Given that FreeBSD src was under a much more rapid
rate of change in that timeframe.)

mcl