public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Mark Galeck <mark_galeck@pacbell.net>
Cc: Bjorn Helgaas <bhelgaas@google.com>, Pavel Machek <pavel@ucw.cz>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: is it desirable to improve the build system?
Date: Fri, 12 Jul 2013 10:32:02 +0200	[thread overview]
Message-ID: <20130712083202.GB5032@netboy> (raw)
In-Reply-To: <1373577734.39761.YahooMailNeo@web182202.mail.bf1.yahoo.com>

On Thu, Jul 11, 2013 at 02:22:14PM -0700, Mark Galeck wrote:
> >The answer to "is it desirable to improve X?" is always "yes."  But
> 
> the only way to make progress in Linux is to actually post patches
> that "improve X."  This is unlike many corporate environments, where
> you might need to get somebody's approval
> 
> 
> Precisely. Please excuse me coming from a corporate background. 
> In corporate, even if you "get somebody's approval", there may be "other stakeholders" who may "feel ownership" etc etc

Yes, your approved project may get canned later. But the point was,
that you aren't allowed to even get started without someone's
approval.

Thanks,
Richard


      reply	other threads:[~2013-07-12  8:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02  0:12 is it desirable to improve the build system? Mark Galeck
2013-07-02  4:45 ` Greg KH
2013-07-02  8:46   ` Mark Galeck
2013-07-02 14:51     ` Greg KH
2013-07-11 11:38 ` Pavel Machek
2013-07-11 20:40   ` Bjorn Helgaas
2013-07-11 21:22     ` Mark Galeck
2013-07-12  8:32       ` Richard Cochran [this message]

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=20130712083202.GB5032@netboy \
    --to=richardcochran@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark_galeck@pacbell.net \
    --cc=pavel@ucw.cz \
    /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