From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jun 23
Date: Tue, 23 Jun 2015 06:59:43 -0700 [thread overview]
Message-ID: <20150623135943.GB9454@kroah.com> (raw)
In-Reply-To: <87twty66gp.fsf@x220.int.ebiederm.org>
On Tue, Jun 23, 2015 at 05:53:58AM -0500, Eric W. Biederman wrote:
>
> Stephen could you please drop the kdbus tree?
What? No, that's not how this works. That's not how any of this works.
> There was some significant work that was identified last merge window
> that has not yet been done, and who knows when it will be done.
> Certainly the recent sd-bus API announcement strongly suggests that
> there are no plans to perform such work.
>
> Having the kdbus tree in linux-next with the implicit suggestion that a
> pull request will be sent to Linus this merge window before the problems
> are addressed and we will have to repeat the mess from last merge window
> keeps me up at night.
Code sitting in linux-next keeps you awake? I think you need to
exercise more so that you can sleep better :)
> So to avoid the appearance that the kdbus folks are continuing to
> ignoring feedback can we please keep the kdbus tree out of linux-next
> until it is ready to be merged?
We are not ignoring _constructive_ feedback, please realize the
difference.
First Andy does a preemptive NAK of a pull request that was never sent,
and now you want to kick it out of linux-next for no valid reason. If I
was an insecure person, I'd think that there are some people in the
kernel community who don't like me at the moment.
This is just getting ridiculous.
greg k-h
next prev parent reply other threads:[~2015-06-23 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 8:18 linux-next: Tree for Jun 23 Stephen Rothwell
2015-06-23 10:53 ` Eric W. Biederman
2015-06-23 13:59 ` Greg Kroah-Hartman [this message]
2015-06-23 15:33 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2025-06-23 6:52 Stephen Rothwell
2023-06-23 5:02 Stephen Rothwell
2022-06-23 6:57 Stephen Rothwell
2021-06-23 12:32 Stephen Rothwell
2020-06-23 6:28 Stephen Rothwell
2017-06-23 7:13 Stephen Rothwell
2016-06-23 7:03 Stephen Rothwell
2014-06-23 5:07 Stephen Rothwell
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=20150623135943.GB9454@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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