From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from secure.elehost.com (secure.elehost.com [185.209.179.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1C0841779BD for ; Fri, 27 Sep 2024 12:23:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.209.179.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727439825; cv=none; b=M7+O7p9NGR0UjmQLr6zXTJcrvRTM55sCcNZCjSxcPJ18USv3tkjEG+omAVt7rQy+c4whaGT79PVknX+byRJWyC7qesZXtVc72EtkYL3YZ15Elzdrnr9Ilk1GX80ra12Xncqz32jc+ei2mHE0UumEqAfKQWZMgpe7AVqTDMzY0EU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727439825; c=relaxed/simple; bh=/HrEFdz8pcv8NOalZnnvnyR0/AWIvUL9LiwKsBSsZec=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=EePdw/ZobP3JUAVOKyUplXMKxP4NiNK4RzqCYLrF2BbbuAlwF/LOSoN1hMDHXx/vP+7zyI/HeHIoXBnIR1nUdj0Pxg58OvRAfNxVf20LpE3Wzp6rQOAsL1hCISrAGTnOXneS/Uqd5txOPLScRflRq2UF2y6MyZ7iN0Z3jrbzaKY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=nexbridge.com; spf=pass smtp.mailfrom=nexbridge.com; arc=none smtp.client-ip=185.209.179.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=nexbridge.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=nexbridge.com X-Virus-Scanned: Debian amavisd-new at secure.elehost.com Received: from Mazikeen (pool-99-228-67-183.cpe.net.cable.rogers.com [99.228.67.183]) (authenticated bits=0) by secure.elehost.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 48RCNaEB1890185 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 27 Sep 2024 12:23:36 GMT Reply-To: From: To: "'Sean Allred'" Cc: , "'Taylor Blau'" , References: <053f01db0b79$0d885b30$28991190$@nexbridge.com> <00a501db0db2$94d505d0$be7f1170$@nexbridge.com> <18d732da-ad34-4a45-b59f-cf2cb3c7238b@gmail.com> <018401db0ed3$667bcf80$33736e80$@nexbridge.com> In-Reply-To: Subject: RE: [TOPIC 01/11] Rust Date: Fri, 27 Sep 2024 08:23:31 -0400 Organization: Nexbridge Inc. Message-ID: <032401db10d8$141962f0$3c4c28d0$@nexbridge.com> Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Content-Language: en-ca Thread-Index: AQF24rJ2Q0W9JcDOH4N3ZxazDM0CYQHP+YxMAoJn3JIBrepyAwFv0IQDAQwByIYCD0om0QJxxC41sswBCxA= On September 27, 2024 5:38 AM, Sean Allred wrote: > writes: >> I do not know whether Rust will never be available. The policy is that >> the Rust maintainers must sanction and approve any ports. I have tried >> to get approval and have not been able to do so. It is not for a lack of trying. > >I do not see a proposal for "NonStop" in a pull request filed against rust- >lang/rust[2] per the process laid out by [1]; can you point me to where you >submitted this request? > >[1]: https://doc.rust-lang.org/rustc/target-tier-policy.html >[2]: https://github.com/rust-lang/rust/pulls?q=is%3Apr+nonstop I will investigate where this went.