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] [thread-next>] [day] [month] [year] [list]
Message-ID: <553486C9.4040700@free-electrons.com>
Date:	Mon, 20 Apr 2015 06:55:37 +0200
From:	Michael Opdenacker <michael.opdenacker@...e-electrons.com>
To:	Jiri Kosina <jkosina@...e.cz>
CC:	edubezval@...il.com, rdunlap@...radead.org, joe@...ches.com,
	akpm@...ux-foundation.org, arend@...adcom.com,
	gregkh@...uxfoundation.org, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [RESEND][TRIVIAL] treewide: fix occurrences of "the the
 "

Hi Jiri,

On 03/27/2015 10:34 AM, Jiri Kosina wrote:
> On Thu, 26 Mar 2015, Michael Opdenacker wrote:
>
>>>  222 files changed, 493 insertions(+), 258 deletions(-)
>> Is this patch getting too big (and getting bigger and bigger) to be ever
>> merged?
>>
>> Unless you tell me otherwise, I'm thinking about splitting it into
>> several patches, one for each subsystem. That would unnecessarily
>> increase the number of commits for the same thing, what else can we do?
> Quite frankly, this is quite painful (compared to the "importance" of the 
> patch) to maintain over several months in trivial.git, because it's going 
> to get conflicts to no good avail all over the place over time.
>
> I think the best thing to do is to send patches like this directly to 
> Linus at the end of merge window and see if he's willing to accept it or 
> not.

Thanks for the sound advice.

Linus, as we are getting closer to the end of the merge window, here's a
patch (in my next e-mail) against your current tree removing many
occurrences of "the the " in the kernel source code. I hope you can
merge it at this stage. This way we will just have one commit in the
tree instead of many more if I had to go through multiple maintainers.

Thanks in advance,

Michael.

-- 
Michael Opdenacker, CEO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
+33 484 258 098


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ