[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d8237d5151e108f969628302c22e27dda3860bdd.camel@perches.com>
Date: Thu, 15 Oct 2020 15:53:15 -0700
From: Joe Perches <joe@...ches.com>
To: Bhaskar Chowdhury <unixbhaskar@...il.com>
Cc: akpm@...ux-foundation.org, colin.king@...onical.com,
sfr@...b.auug.org.au, wangqing@...o.com, david@...hat.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 Fri, 2020-10-16 at 04:19 +0530, Bhaskar Chowdhury wrote:
> On 14:10 Thu 15 Oct 2020, Joe Perches wrote:
> > On Thu, 2020-10-15 at 19:24 +0530, Bhaskar Chowdhury wrote:
> > > On 06:38 Thu 15 Oct 2020, Joe Perches wrote:
> > > > On Thu, 2020-10-15 at 18:53 +0530, Bhaskar Chowdhury wrote:
> > > > > Fix the space in the middle in below entry.
> > > > >
> > > > > memry||memory
> > > > []
> > > > > diff --git a/scripts/spelling.txt b/scripts/spelling.txt
> > > > []
> > > > > @@ -885,7 +885,7 @@ meetign||meeting
> > > > > memeory||memory
> > > > > memmber||member
> > > > > memoery||memory
> > > > > -memry ||memory
> > > > > +memry||memory
> > > >
> > > > No. Don't post a bad patch, assume
> > > > it's applied and then post a fix to
> > > > the bad patch as v2.
> > > >
> > > > Send a single clean patch.
> > > >
> > >
> > > Not sure what you mean...could you elaborate...don't know what is going on..>
> >
> > You sent a patch with a defect
>
> Who doesn't???
No one.
> > You sent a V2 patch that just corrects the defect in the first patch.
>
> That's how it is working here for long time ...I am not sure about your
> involvement.
wrong. Your first patch has not been, and should
not be applied, as it has a trivial known defect.
> Please don't unnecessarily streach thing ...we have other things to do ...do
> not bringing "new rules" here for the sake of it.
It's not a new rule.
Don't introduce patches with defects.
Powered by blists - more mailing lists