linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@fifo99.com>
To: davidb@codeaurora.org, bryanh@codeaurora.org
Cc: arnd@arndb.de, olof@lixom.net, khilman@deeprootsystems.com,
	linux-arm-msm@vger.kernel.org
Subject: the future of qualcomm SoC in linux
Date: Fri, 1 Nov 2013 10:11:13 -0700	[thread overview]
Message-ID: <20131101171112.GA17267@fifo99.com> (raw)


David, Bryan,

In general this community wants all code maintained. Your intentions seem to be
that you want to push code, but you want to orphan it fairly quickly after you
push the code. I know this is true having worked with both of you and many of
your developers, and recent events seem to prove it.

It's fine if you don't want to maintain the code you push, but it's better for
us as a community if some one does maintains the code long term (10-15 years).

Linux also fosters community development so that people with devices can submit
patches or add extensions to existing code. It's my believe that you don't want
that, and have no intentions of supporting it for any of your platforms or for
any device that is created with your chips.

Since both of you seem un-willing to do these things, I suggesting this compromise. I
maintain the code long term for all Qualcomm platforms new and old, you submit
patches to me. If you don't want me to do this, or don't trust me to do it,
that's fine too just find someone else willing to maintain all the code long term.

Daniel

             reply	other threads:[~2013-11-01 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 17:11 Daniel Walker [this message]
2013-11-01 18:02 ` the future of qualcomm SoC in linux Bill Gatliff

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=20131101171112.GA17267@fifo99.com \
    --to=dwalker@fifo99.com \
    --cc=arnd@arndb.de \
    --cc=bryanh@codeaurora.org \
    --cc=davidb@codeaurora.org \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).