unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 61489@debbugs.gnu.org, 61490@debbugs.gnu.org, hi-angel@yandex.ru
Subject: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768
Date: Thu, 23 Feb 2023 18:40:35 +0200	[thread overview]
Message-ID: <83pma0pc70.fsf@gnu.org> (raw)
In-Reply-To: <87edqg8jrj.fsf@gmail.com> (message from Robert Pluim on Thu, 23 Feb 2023 16:49:04 +0100)

> Cc: 61489@debbugs.gnu.org, 61490@debbugs.gnu.org
> From: Robert Pluim <rpluim@gmail.com>
> Date: Thu, 23 Feb 2023 16:49:04 +0100
> 
> >>>>> On Thu, 23 Feb 2023 18:30:00 +0300, Konstantin Kharlamov <hi-angel@yandex.ru> said:
> 
>     Konstantin> So, it's been a week since version 2 was posted and 10-11 days since I started
>     Konstantin> using the change locally. Everything has been nice and dandy, and in absence of
>     Konstantin> further comments, I wonder if somebody with write permissions could merge this
>     Konstantin> patch?
> 
> Iʼve had no issues with it. Eli? Does this require 'Copyright-paperwork-exempt: yes'?

Yes, it does.





  parent reply	other threads:[~2023-02-23 16:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 20:00 bug#61490: [PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵ Konstantin Kharlamov
2023-02-13 20:00 ` bug#61489: [PATCH 1/1] " Konstantin Kharlamov
     [not found]   ` <handler.61489.B.167631844622733.ack@debbugs.gnu.org>
2023-02-13 20:05     ` bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵) Konstantin Kharlamov
2023-02-14  3:29       ` Eli Zaretskii
2023-02-14  6:45         ` Konstantin Kharlamov
2023-02-14  6:56           ` Konstantin Kharlamov
2023-02-14  8:20             ` Robert Pluim
2023-02-14  8:22               ` Konstantin Kharlamov
2023-02-14  8:29                 ` Konstantin Kharlamov
2023-02-14 13:26               ` Eli Zaretskii
2023-02-15  7:03                 ` bug#61489: Open a bug report with git-send-email (was: bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵)) Kévin Le Gouguec
2023-02-13 22:30   ` bug#61489: [PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵ Ihor Radchenko
2023-02-16 15:07   ` bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768 Konstantin Kharlamov
2023-02-23 15:30     ` Konstantin Kharlamov
2023-02-23 15:49       ` Robert Pluim
2023-02-23 15:53         ` Konstantin Kharlamov
2023-02-23 15:57           ` bug#61490: " Robert Pluim
2023-02-23 16:05             ` Konstantin Kharlamov
2023-02-23 16:34               ` Robert Pluim
2023-02-23 16:41           ` bug#61489: bug#61490: " Eli Zaretskii
2023-02-24 10:50             ` Robert Pluim
2023-02-27 10:30               ` bug#61490: " Konstantin Kharlamov
2023-02-23 16:40         ` Eli Zaretskii [this message]
2023-03-04 11:26     ` Eli Zaretskii
2023-03-04 15:00       ` Eli Zaretskii
2023-03-04 15:33         ` Konstantin Kharlamov
2023-03-04 18:58           ` Konstantin Kharlamov
2023-03-04 19:53             ` Eli Zaretskii
2023-03-04 19:58               ` Konstantin Kharlamov
2023-03-05  5:47                 ` Eli Zaretskii
     [not found] ` <handler.61490.B.167631845222751.ack@debbugs.gnu.org>
2023-02-13 20:05   ` bug#61490: Acknowledgement ([PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵) Konstantin Kharlamov
2023-02-16  4:59 ` bug#61490: [PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵ Richard Stallman
2023-02-16  6:46   ` Konstantin Kharlamov
2023-02-16  9:31   ` Gregory Heytings
2023-02-21  5:22     ` bug#61490: [PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵ Richard Stallman
2023-02-16 15:05 ` bug#61490: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768 Konstantin Kharlamov
2023-02-16 15:29   ` Robert Pluim
2023-02-16 16:48     ` Konstantin Kharlamov
2023-02-16 17:00       ` Konstantin Kharlamov
2023-02-16 17:02       ` Robert Pluim
2023-03-03 10:44 ` Konstantin Kharlamov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pma0pc70.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61489@debbugs.gnu.org \
    --cc=61490@debbugs.gnu.org \
    --cc=hi-angel@yandex.ru \
    --cc=rpluim@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).