From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs 28.2 released Date: Thu, 15 Sep 2022 08:37:40 +0300 Message-ID: <83edwd19ln.fsf@gnu.org> References: <87wna8ia11.fsf@red-bean.com> <835yhs57m6.fsf@gnu.org> <83tu5b4h3d.fsf@gnu.org> <87v8pr1l5v.fsf@gnus.org> <871qsfmluh.fsf@gmail.com> <87leql6gy0.fsf@gnus.org> <83v8pp274u.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29027"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, rpluim@gmail.com, kfogel@red-bean.com, emacs-devel@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Sep 15 07:42:27 2022 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 1oYhdr-0007M1-0o for ged-emacs-devel@m.gmane-mx.org; Thu, 15 Sep 2022 07:42:27 +0200 Original-Received: from localhost ([::1]:35306 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oYhdp-0000lR-MU for ged-emacs-devel@m.gmane-mx.org; Thu, 15 Sep 2022 01:42:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43696) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYhZN-0007Ny-Tv for emacs-devel@gnu.org; Thu, 15 Sep 2022 01:37:50 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52756) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYhZN-0000rY-6H; Thu, 15 Sep 2022 01:37:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=yjaNDSB931FYNuAD299yqEF3lRahQOaoEpoEDLdl9RI=; b=PC/OAMtmf7S7 UtU0rsx4/svaFpMD7TbWfX2c/7pn9Px+q64xaCXxu8wcnCjwVVXG3OSmMs5WonHM32W8PDGf6p96B Exa4zREG+psOtIYYPiwiGNcpU7kS+oIrMjx2lW6VvvH0jfdoD9LUd/j5559YlpTQPWPcQGnxpoLtQ 0svT40FyE/WUrVqH7vexDkhsrD+JCOaz9D1HRbWK7Hf6nY6dtVcoE84PQxHCkzmTMPBOQMTp8ycOn f8ORvK6Y6571VPZ2rlpihlRgfZ30i0kVjUBZHEkaBwlhoOm9Z0uSrbWy+KRcS6wY6oL9Mg8hhmieF Z30pKjnZjoJvMMzUqXqxCw==; Original-Received: from [87.69.77.57] (port=4918 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYhZM-0008OR-LM; Thu, 15 Sep 2022 01:37:48 -0400 In-Reply-To: (message from Stefan Kangas on Wed, 14 Sep 2022 15:50:48 -0700) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:295377 Archived-At: > From: Stefan Kangas > Date: Wed, 14 Sep 2022 15:50:48 -0700 > Cc: rpluim@gmail.com, kfogel@red-bean.com, emacs-devel@gnu.org > > Eli Zaretskii writes: > > >> > See here for the result: > >> > > >> > https://www.gnu.org/software/emacs/news/NEWS.28.2.html > >> > >> Great; that looks really good. > > > > I don't like the result at all, and like even less what is intended to > > be its usage. > > To clarify, the intention is to replace the link on > > https://www.gnu.org/software/emacs/#Releases > > which currently points to > > https://www.gnu.org/software/emacs/news/NEWS.28.2 > > with > > https://www.gnu.org/software/emacs/news/NEWS.28.2.html First, this was not what Karl was talking about (AFAIU, and it sounds like I might be misunderstanding -- again). He asked to include a link in the email announcement we post to various GNU mailing lists, whereas the above replaces the link on the Emacs Web site, which is a different place. I was talking about what I perceived was Karl's request. Second, to evaluate your proposal, please describe what is needed (which commands and packages, and how to use them) to produce this HTML version. Also, how will this HTML version be maintained, after it is produced. I don't think you described all that in detail; apologies if I missed something.