From: Masahiro Yamada <masahiroy@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [GIT PULL] kconfig: localmodconfig: Minor clean ups to streamline_config.pl
Date: Fri, 31 Jan 2020 11:08:59 +0900 [thread overview]
Message-ID: <CAK7LNATryPUSTm8wPTFHO=E5f=sVPM4T0UxT=BF2qeyVehsH6Q@mail.gmail.com> (raw)
In-Reply-To: <20200130143941.23a0e217@gandalf.local.home>
On Fri, Jan 31, 2020 at 4:39 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Fri, 31 Jan 2020 03:30:37 +0900
> Masahiro Yamada <masahiroy@kernel.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 :-/
>
Steven,
OK, I see. I will also try my best to send a notice email.
I want to avoid a situation where two people
are picking up the same patches without noticing each other.
Linus,
If you have not pulled this one yet,
could you ignore it?
I will soon send pull requests for Kbuild + Kconfig,
which includes the same patches.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2020-01-31 2:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 17:22 [GIT PULL] kconfig: localmodconfig: Minor clean ups to streamline_config.pl Steven Rostedt
2020-01-30 18:30 ` Masahiro Yamada
2020-01-30 19:39 ` Steven Rostedt
2020-01-31 2:08 ` Masahiro Yamada [this message]
2020-01-31 2:37 ` Steven Rostedt
2020-01-31 2:41 ` Steven Rostedt
2020-01-31 3:15 ` Masahiro Yamada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK7LNATryPUSTm8wPTFHO=E5f=sVPM4T0UxT=BF2qeyVehsH6Q@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).