From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Joseph Myers Newsgroups: gmane.comp.lib.glibc.alpha Subject: Re: riscv: fmax/fmin sNaN fix Date: Thu, 22 Feb 2018 20:42:40 +0000 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Trace: blaine.gmane.org 1519332049 11402 195.159.176.226 (22 Feb 2018 20:40:49 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 22 Feb 2018 20:40:49 +0000 (UTC) User-Agent: Alpine 2.20 (DEB 67 2015-01-07) Cc: Carlos O'Donell , To: DJ Delorie Original-X-From: libc-alpha-return-90502-glibc-alpha=m.gmane.org@sourceware.org Thu Feb 22 21:40:45 2018 Return-path: Envelope-to: glibc-alpha@blaine.gmane.org DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; q=dns; s=default; b=rkESW imfUBoleiL0sl2otUSvR+ihuIu19JpphCU1iQIhwLuIedgvL6pgLxClE+XvlAFgd 8ifOAJbLgIkdq50rNkA8thhx4/n+xCQTKz4nbcuIheDjxrlvpusKhq2sG4rAMwy/ iuYvDw4prQs2l4rD1AIprXXgLV4ieUdNirjeq0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; s=default; bh=pGCu8XPCDp+ L0FE/8ZpZKF4seNU=; b=xL3n24AoMwcbe0p8OxCKBTvP0UdZAvZXp2E9UNbAu37 jui8tggBYVC6ZcC5YmvfTwOjsJDwedjuyhaYjjumSgHyMKiq/yZSOhCyWkKQcS9o DYB5tE5jO7RgtmeDHegKTflBTt7W3fWfOAL7RyLmTPo4kqVb5IH+m+HYGQiVJiLI = Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Original-Sender: libc-alpha-owner@sourceware.org Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy= X-HELO: relay1.mentorg.com In-Reply-To: X-ClientProxiedBy: svr-ies-mbx-02.mgc.mentorg.com (139.181.222.2) To SVR-IES-MBX-03.mgc.mentorg.com (139.181.222.3) Xref: news.gmane.org gmane.comp.lib.glibc.alpha:82834 Archived-At: Received: from server1.sourceware.org ([209.132.180.131] helo=sourceware.org) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eoxfY-0002Sc-BT for glibc-alpha@blaine.gmane.org; Thu, 22 Feb 2018 21:40:44 +0100 Received: (qmail 1597 invoked by alias); 22 Feb 2018 20:42:47 -0000 Received: (qmail 1574 invoked by uid 89); 22 Feb 2018 20:42:46 -0000 On Thu, 22 Feb 2018, DJ Delorie wrote: > "Carlos O'Donell" writes: > > If there is a release out for RISC-V alrady, then this needs a bug number. > > If that's the rule, then *every* change needs a bug number, because > there's always a "release out" for some platform... It's for changes that fix a bug that was user-visible in a release. (My interpretation of being user-visible in a release excludes bugs that caused the build to be broken, or bugs in the manual, or bugs in a testcase, or test failures such as check-localplt where a failure only indicates an optimization issue rather than an actual misbehavior in the installed glibc.) New features and internal cleanups never need bugs filed in Bugzilla; likewise fixes for issues introduced on master after the last release, and for bugs in new features added since the last release. We want the NEWS file to be as complete as possible regarding user-visible changes. For new features and significant optimizations, entries are added to the relevant section of the NEWS file by hand (and should be included in the patches adding such features). For miscellaneous bugfixes, the only reference in NEWS may be in the automatically-generated list of fixed bugs. For that list to be as complete as possible, a bug needs filing in Bugzilla before being fixed, then marking as FIXED with target milestone set to the next release once the fix is checked in; that way, it will be automatically included in the list generated by scripts/list-fixed-bugs.py. > (distinct from "backports to release branches need a bug number, for > tracking", if that's a rule) We don't have such a rule. Backports to release branches should be posted to the libc-stable list. -- Joseph S. Myers joseph@codesourcery.com