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: <20200130143941.23a0e217@gandalf.local.home>
Date:   Thu, 30 Jan 2020 14:39:41 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Masahiro Yamada <masahiroy@...nel.org>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>
Subject: Re: [GIT PULL] kconfig: localmodconfig: Minor clean ups to
 streamline_config.pl

On Fri, 31 Jan 2020 03:30:37 +0900
Masahiro Yamada <masahiroy@...nel.org> wrote:

> 
> I know you are the author of streamline_config,
> but actually did not know you were collecting
> patches for this particular file.
> 
> 
> I did not receive a notice email from you,
> nor did these commits appear in linux-next at all.
> Could you send a notice email when
> you pick up a patch next time?
> (Sorry, I also forgot to send a email.
> I will drop them from my tree.)
> 


It's my fault. I was looking through my inbox (actually my local
patchwork that reads my inbox) and saw these patches from back in
December. I then went to my "kconfig" development git repo, and saw I
pulled them in, but never actually pushed them anywhere (not even to my
"staging" machine where I stage my pushes to kernel.org).

This being the merge window, I rushed to get them in as they were very
trivial changes. This isn't my normal flow, it was more "Oh crap! I
forgot about these, let me get them in now".

If you have them in your tree, I'm fine with them getting in from there.
I should have looked in next (I only looked to see if Linus already had
them).

Note, since this file hasn't been updated in years, my kconfig
'for-next' branch has been removed from linux-next :-/

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ