[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768
From: |
Robert Pluim |
Subject: |
bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768 |
Date: |
Thu, 23 Feb 2023 17:34:12 +0100 |
>>>>> On Thu, 23 Feb 2023 19:05:22 +0300, Konstantin Kharlamov
>>>>> <hi-angel@yandex.ru> said:
Konstantin> On Thu, 2023-02-23 at 16:57 +0100, Robert Pluim wrote:
>> > > > > > On Thu, 23 Feb 2023 18:53:02 +0300, Konstantin Kharlamov
>> > > > > > <hi-angel@yandex.ru> said:
>>
>> Konstantin> On Thu, 2023-02-23 at 16:49 +0100, Robert Pluim wrote:
>> >> > > > > > 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'?
>>
>> Konstantin> No, I have a copyright assignment with GNU for Emacs,
it's
>> just that I don't write permissions :)
>>
>> OK. I canʼt find any commits in your name using 'hi-angel@yandex.ru>'
>> as the email address, is it under a different one?
Konstantin> Well, the "Hi-Angel" is my old nickname, so I typically upcase
it, including
Konstantin> inside the email address. So my email inside git config is
"email =
Konstantin> Hi-Angel@yandex.ru", and similarly to find my commits with
`git-log` you gotta
Konstantin> use a:
Konstantin> git log --author="Hi-Angel@yandex.ru"
TIL that I havenʼt turned on enough case-insensitivity in my git
aliases :-)
Robert
--
- bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵), (continued)
bug#61489: [PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵, Ihor Radchenko, 2023/02/13
bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Konstantin Kharlamov, 2023/02/16
- bug#61490: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Konstantin Kharlamov, 2023/02/23
- bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Robert Pluim, 2023/02/23
- bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Konstantin Kharlamov, 2023/02/23
- bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Robert Pluim, 2023/02/23
- bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Konstantin Kharlamov, 2023/02/23
- bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768,
Robert Pluim <=
bug#61489: bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Eli Zaretskii, 2023/02/23
bug#61489: bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Robert Pluim, 2023/02/24
bug#61489: bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Konstantin Kharlamov, 2023/02/27
bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Eli Zaretskii, 2023/02/23
Message not available
bug#61490: [PATCH 0/1] Increase BLOCK_ALIGN from 2¹â°to 2¹âµ, Richard Stallman, 2023/02/16
bug#61490: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Konstantin Kharlamov, 2023/02/16