linux-kernel - Re: [PATCH V2] scripts: spelling: Remove space in the entry memry to memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <eb71aa65-20c1-44e9-4104-582be44c4f7a@redhat.com>
Date:   Fri, 16 Oct 2020 10:10:20 +0200
From:   David Hildenbrand <david@...hat.com>
To:     Bhaskar Chowdhury <unixbhaskar@...il.com>,
        Joe Perches <joe@...ches.com>, akpm@...ux-foundation.org,
        colin.king@...onical.com, sfr@...b.auug.org.au, wangqing@...o.com,
        xndchn@...il.com, luca@...aceresoli.net, ebiggers@...gle.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] scripts: spelling: Remove space in the entry memry to
 memory

On 16.10.20 05:49, Bhaskar Chowdhury wrote:
> On 20:19 Thu 15 Oct 2020, Joe Perches wrote:
>> On Fri, 2020-10-16 at 04:38 +0530, Bhaskar Chowdhury wrote:
>>> On 16:06 Thu 15 Oct 2020, Joe Perches wrote:
>>>> On Fri, 2020-10-16 at 04:25 +0530, Bhaskar Chowdhury wrote:
>>>>> You have all flawed understanding...please stay away ..
>>>>> if you don't understand something...
>>>>
>>>> <chuckle>  You're funny.
>>>>
>>>> You're wrong, but you're still funny.
>>>>
>>>>
>>> ROFL ..you too...what a waste of time ...shame that I am engage this kind of
>>> conversation ...heck
>>
>> Your tone doesn't become you.
> Same  goes you too...
> 
>> Please try to be polite next time.
> 
> Please stop sending unnecessary "reviews" too. Thanks. If I need ,I will ask.
> 
> Well, didn't I appreciate your feedback first time?? It the following that
> stupid and garbage .
> 
>> I'm rather familiar with the appropriate process.
>>
>> $ git shortlog -n -s --author="Joe Perches" --author="Bhaskar Chowdhury"
>>   3227  Joe Perches
>>      8  Bhaskar Chowdhury
>>      1  Joe Perches via samba-technical
> 
> Never doubt that ..but you clinging on something not true is surprise me...I
> believe you do better next time.
> 
> This is the most "useless" thread I have ever been...
> 
> Stop propagating it ...>
> 

Honestly, I really don't want to wake up, check my mails, and read such 
toxic crap. Stop it, this is not how we communicate on these lists. Period.

If you have the urge to scream at each other (or make fun of each 
other), do that off-list (or even better: don't!).

I haven't read the whole discussion, here is my understanding:

A new patch series version supersedes older ones, meaning it should be 
completely self-contained. Just as if you're buying a new version of a 
car, they won't be sending parts to replace.

Imagine you're at V37, no reviewer will go through v1..V37 and apply 
delta updates. When a reviewer sees a new version, the old ones are 
discarded.

Now, when it comes to *simple fixups* like here, the process depends a 
little bit on the subsystem + maintainer, and it's best to ask how to 
proceed.

Option 1: Send a new version that's completely self-contained.

Option 2: Ask the maintainer to fixup while applying/before sending 
upstream.

Option 3: Send an *unversioned* fixup patch as reply to the problematic 
patch and ask to squash that into the original patch.

Of course, it's different when the patch is already upstream. Then, a 
fix/cleanup should mention the original, problematic commit.

-- 
Thanks,

David / dhildenb