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

Linux Kernel based project in git

From
Ggit@eisendle.net <git@eisendle.net>
Date
Feb 2, 2010, 09:05 UTC
Message-ID
<9da7f2802f639777acfeb38eb1e3db90.squirrel@webmail.eisendle.net>
Hi,

I'm rather new to this mailing list so I hope this is the right place for my question :-)

We recently moved one of our projects over from SVN to git. This project is basically a Linux BSP for an ARM9 based processor using Kernel 2.6.22.

For release we always generate 3 patches:
- BSP patch
- USB patch (since USB part is an external patch comming from a 3rd party)
- WiFi patch (same as for USB)

So my question is: What's the best way for handling this inside the git repository?

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.

Is this a useful approach or are there other, better ways for generating the three patches and compiling testing the whole thing?

Thanks! Christian.

Next: Avery Pennarun
Message 1 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.