git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Kelly <steveire@gmail.com>
To: git@vger.kernel.org
Subject: Re: Linux Kernel based project in git
Date: Sat, 06 Feb 2010 12:43:36 +0100	[thread overview]
Message-ID: <hkjkl7$8eg$1@ger.gmane.org> (raw)
In-Reply-To: be6731d603701c3c5befc79613fd451b.squirrel@webmail.eisendle.net

Christian Eisendle wrote:
>>> IMHO it would make sense to have 3 branches (BSP, USB, WiFi) each based
>>> on
>>> unmodified 2.6.22 Kernel. USB and WiFi branch is used for generating the
>>> patch and for applying possible fixes. BSP branch for actual BSP related
>>> feature development and fixes.
>>> The changes in these branches are merged into the master branch which is
>>> used for compiling/testing the whole BSP.
>>
>> Are you planning to submit these patches upstream at any point?  If
>> not, it might be easiest to just jam them all together in one branch
>> and not look back.  Since it seems like they probably affect quite
>> different parts of the code, you could always extract a clean set of
>> patches *later* and submit those patches upstream.
> 
> For BSP I plan to upstream eventually.
> 
> The basic idea was to divide the project in three different patches since
> USB and WiFi comes from a third party and is not released under GPL (well,
> different story...)

Do you distribute this kernel?

      reply	other threads:[~2010-02-06 11:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02  9:05 Linux Kernel based project in git git
2010-02-02 19:53 ` Avery Pennarun
2010-02-03  8:32   ` Christian Eisendle
2010-02-06 11:43     ` Stephen Kelly [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='hkjkl7$8eg$1@ger.gmane.org' \
    --to=steveire@gmail.com \
    --cc=git@vger.kernel.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).