From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Corwin Brust Newsgroups: gmane.emacs.devel Subject: Re: Windows Binaries for Emacs 28.2 released Date: Tue, 13 Sep 2022 21:56:43 -0500 Message-ID: References: <834jxb414i.fsf@gnu.org> <87h71bb04j.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26961"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: =?UTF-8?Q?=C3=93scar_Fuentes?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 14 04:58:01 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 1oYIbB-0006oz-CL for ged-emacs-devel@m.gmane-mx.org; Wed, 14 Sep 2022 04:58:01 +0200 Original-Received: from localhost ([::1]:33400 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oYIb9-0006a3-N0 for ged-emacs-devel@m.gmane-mx.org; Tue, 13 Sep 2022 22:57:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49408) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYIa8-0005Hp-S0 for emacs-devel@gnu.org; Tue, 13 Sep 2022 22:56:56 -0400 Original-Received: from mail-oa1-f49.google.com ([209.85.160.49]:38745) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oYIa7-0008M4-95 for emacs-devel@gnu.org; Tue, 13 Sep 2022 22:56:56 -0400 Original-Received: by mail-oa1-f49.google.com with SMTP id 586e51a60fabf-1278624b7c4so37467560fac.5 for ; Tue, 13 Sep 2022 19:56:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date; bh=maKTQRsfG/qvgVobRJsic55Cxrqz88RH6bVroJzTTe4=; b=oVYx5O8ywSoCI1G8xISDI3uf5YD03HoRlyadByb/qSqvh4hsJaV0EvZ1H+jK+BL+i6 FlV1SXKG8NTzAtzAMszikq+/W24yYaZjMFjVP8tfcvtO8KBNDCHVuXVjPoGFF5SsXs4O Dr2W/KPBb5cYG/rMht4WFhv4xMjrlCphZfGgS2q0mbxjpFngA7ClFI1j+sb8330eergW YqmOiPuHV45TfpeS2KlANiDWSnsGkRtE+45kNHvc0b+s8s+GnMlHPIthyLhfLQy+zjXT 7AQIeI6yozw+uNzeLk3u7QJoOjBeBowN9y0WFNbtCv/9FJJvJboNfUrWNeugk6L0qDDY 8MCw== X-Gm-Message-State: ACgBeo1p13s/NogVGycpaHO/wG0QKYdNr9bV1JqXQZ/WGjrOXyZK3tLp kKeRhFLGWH9uENDm5zHeT73XaTZg9s5l7o7gOFc= X-Google-Smtp-Source: AA6agR5ekp46k7RETNqt6s82L5XhuTT9EvTycJUjLGqkFuBhMmNXR9Bitwib+hkDrVW1WHDYwVjFQjSj63NH0Stsxxg= X-Received: by 2002:a05:6870:460e:b0:12b:14cc:aa0 with SMTP id z14-20020a056870460e00b0012b14cc0aa0mr1109196oao.279.1663124213941; Tue, 13 Sep 2022 19:56:53 -0700 (PDT) In-Reply-To: <87h71bb04j.fsf@telefonica.net> Received-SPF: pass client-ip=209.85.160.49; envelope-from=mplscorwin@gmail.com; helo=mail-oa1-f49.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, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action 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:295290 Archived-At: On Tue, Sep 13, 2022 at 1:27 PM =C3=93scar Fuentes wrote: > > FWIW, the MSYS2/Mingw64 package which is going to be published soon does > not show this problem. It seems likely to have been an error on my part in creating the particular snapshot release that the report relates to. I haven't been able to recreate the problem so far, nor reproduce it using any of the release builds I've made recently.