git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Linux Kernel based project in git

From
SKStephen Kelly <steveire@gmail.com>
Date
Feb 6, 2010, 11:43 UTC
Message-ID
<hkjkl7$8eg$1@ger.gmane.org>
In-Reply-To
<be6731d603701c3c5befc79613fd451b.squirrel@webmail.eisendle.net>
Christian Eisendle wrote:
Show 19 quoted lines
>>> 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?
Previous: Christian Eisendle
Message 4 of 4 in “Linux Kernel based project in git”
  1. git@eisendle.netFeb 2, 2010
  2. Avery PennarunFeb 2, 2010
  3. Christian EisendleFeb 3, 2010
  4. Stephen KellyFeb 6, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.