mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jerry Kirk <jkirk865@gmail.com>
To: barebox@lists.infradead.org
Subject: How should a new internally developed board be handled?
Date: Fri, 8 Jun 2012 14:48:24 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120608T163815-186@post.gmane.org> (raw)

Our company is developing a new board for the i.MX35 series
for use in various internal products. We do not expect to
ever "sell" this board on the open market.

We recognize the "public" license and are willing to release
any modifications so that others might learn from our changes
in order to improve their systems.

In this case, is it appropriate for me to begin submitting
patches to define our new (internal only) board and it's
configuration? It would certainly be easier if our changes
were in the tree as we migrate through various versions of
barebox.

Thanks,
  Jerry



_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2012-06-08 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 14:48 Jerry Kirk [this message]
2012-06-15 12:50 ` Jerry Kirk

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=loom.20120608T163815-186@post.gmane.org \
    --to=jkirk865@gmail.com \
    --cc=barebox@lists.infradead.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