From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: Organizing the NEWS file a bit better Date: Sat, 4 Sep 2021 23:08:24 +0200 Message-ID: References: <87wnnwp3g8.fsf@gnus.org> <87mtosnkch.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19349"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Emacs developers To: Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 04 23:10:03 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mMcvK-0004sh-Sm for ged-emacs-devel@m.gmane-mx.org; Sat, 04 Sep 2021 23:10:02 +0200 Original-Received: from localhost ([::1]:52938 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mMcvJ-0006Os-9q for ged-emacs-devel@m.gmane-mx.org; Sat, 04 Sep 2021 17:10:01 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60866) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mMcty-00052O-HC for emacs-devel@gnu.org; Sat, 04 Sep 2021 17:08:38 -0400 Original-Received: from mail-pg1-f169.google.com ([209.85.215.169]:33509) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mMctx-0007xO-1r for emacs-devel@gnu.org; Sat, 04 Sep 2021 17:08:38 -0400 Original-Received: by mail-pg1-f169.google.com with SMTP id c17so2664865pgc.0 for ; Sat, 04 Sep 2021 14:08:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Uvq0B00ujCqKBJgXM+3PqGmeX7dmZ5RuaXKMalkqHd8=; b=mqVo7mVxhFKcu/FjFV+MkIMYdTMeVCu++2l4msSV55PDNO6z4LNX0MWxXeY3Zq1iH1 ykiLgr83PTmoAdfRKL7gqLZUem11OJkWrpwmnA25rNRqVKkYOg5ebD5z8BQTomdfn/kW aCBxbrOa0Sxv6Fr9pAN8J4hK0mnPXqr3+RQ4V475nEEwBdipIGRMS/4zPzMryp8Y3ENV 3CyKgAvYNxwWswM8/Ge0zVK9m6vHpVatcxpz4R+cjGnk8RKyoX/FALkP62kvPBrDpp+Q C2jD2xYkIBx80BQWI9UGvPhxoml8GDqXfeAoGoW7YlI062+IW4fl/ytrGDxiBZPm6smK 6jKA== X-Gm-Message-State: AOAM532CGjXlsZ6iVjBkn+MGBAi28Hbe0UeHtFodY2nSzF03hscleUg6 ENiFle3w0Odto6Wz3KmQDSSL9otwKOBiGfakZO4= X-Google-Smtp-Source: ABdhPJzkcfeSSGwgMr5aS5QAFbhCpDPW6zdn9P/oOHYZCkH7Vbxly+xtK4fT1zPjB3WsGXBWHYZsNhbJ/jhRewsmuCs= X-Received: by 2002:aa7:80d9:0:b029:2ed:49fa:6dc5 with SMTP id a25-20020aa780d90000b02902ed49fa6dc5mr4895382pfn.3.1630789715668; Sat, 04 Sep 2021 14:08:35 -0700 (PDT) In-Reply-To: <87mtosnkch.fsf@gmail.com> Received-SPF: pass client-ip=209.85.215.169; envelope-from=stefankangas@gmail.com; helo=mail-pg1-f169.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:273968 Archived-At: Tim Cross writes: > I think this is an important one. My 'use case' for looking in NEWS is > > 1. See what has changed and may require that I review/update my > configuration. I might read this before upgrading or immediately after. > Being able to identify a specific section which alerts me to > incompatible changes is important. Yup, it seems like we all agree about keeping this section as is. > 2. When I find something not working after an upgrade, I will look to > see if some change may have occurred. For this use case, I tend to use > C-s and search for specific keywords rather than general reading of the > file. Anything which would help in this regard would be useful. Thanks. Your use-case is different from mine, which is to carefully review the file from top to bottom. (I understand that we can't realistically expect most users to do that.) I'm not sure what we could do to improve searching, but ideas are welcome of course.