Re: [PATCH 5.15 00/37] 5.15.96-rc2 review

[Greg Kroah-Hartman <gregkh@linuxfoundation.org>]

On Thu, Feb 23, 2023 at 01:18:31PM -0800, Linus Torvalds wrote:
> On Thu, Feb 23, 2023 at 11:47 AM Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > I can send a patch unless you want to take those changes directly, you
> > have half a commit message there already I think :)
> 
> Not being one of those old fogeys myself, I don't feel hugely motivated to care.
> 
> In fact, I think GNU patch implemented the git patch format extensions
> more than a decade ago, so we might even simply decide that it's past
> time to even worry about this at all.
> 
> In fact, with all the base infrastructure supporting git patches, I'm
> not quite sure just _how_ quilt is able to apply patches without
> dealing with mode bits.
> 
> Does quilt parse the patches and actively remove those lines before
> applying them? Or does quilt have some actual built-in patch
> application code that doesn't depend on GNU patch?
> 
> (Side note: GNU patch may support git patches, but I don't think GNU
> diffutils will generate them, so I guess not all base infrastructure
> supports that fancy new "mode" line)

Quilt should be depending on patch here, I think it's something in my
set of "turn this series of patches into a mbox, split the mbox up into
patches" sequence that is causing the problem.  I'll look into it in the
morning, but for now, I'm blaming my horrid scripts, not git or quilt
just yet...

thanks,

greg k-h