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

Re: Git setup for kernel in-house development + mainstream submissions?

From
Johannes Gilger <heipei@hackvalue.de>
Date
Feb 2, 2009, 07:26 UTC
Message-ID
<gm677g$3io$2@ger.gmane.org>
In-Reply-To
<49861363.1000104@aster.pl>
On 2009-02-01, PaV <pav@aster.pl> wrote:
Show 6 quoted lines
> I would like to kindly ask for suggestions how to setup and use git in a
> company that performs in-house kernel development (drivers mostly) for
> its own devices and would like to occasionaly submit patches for mainstream.
> [...]
> So the proposed setup might be:
> (1) - in-house devel could be done on separate branches for each driver

Do you really want to have separate drivers in the same git repository? Do these drivers share so much code and depend on each other that this would be necessary? If not I'd suggest you think about separate git projects for each driver, unless there is a compelling reason against it.

Greetings, Jojo

-- 
Johannes Gilger <heipei@hackvalue.de>
http://hackvalue.de/heipei/
GPG-Key: 0x42F6DE81
GPG-Fingerprint: BB49 F967 775E BB52 3A81  882C 58EE B178 42F6 DE81
Previous: PaVNext: Matt Graham
Message 2 of 3 in “Git setup for kernel in-house development + mainstream submissions?”
  1. PaVFeb 1, 2009
  2. Johannes GilgerFeb 2, 2009
  3. Matt GrahamFeb 3, 2009

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.