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

David Hildenbrand
2020-10-16T08:10:36Z

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