From: Johannes Gilger <heipei@hackvalue.de>
To: git@vger.kernel.org
Subject: Re: Git setup for kernel in-house development + mainstream submissions?
Date: Mon, 2 Feb 2009 07:26:40 +0000 (UTC) [thread overview]
Message-ID: <gm677g$3io$2@ger.gmane.org> (raw)
In-Reply-To: 49861363.1000104@aster.pl
On 2009-02-01, PaV <pav@aster.pl> wrote:
> 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
next prev parent reply other threads:[~2009-02-02 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 21:25 Git setup for kernel in-house development + mainstream submissions? PaV
2009-02-02 7:26 ` Johannes Gilger [this message]
2009-02-03 4:13 ` Matt Graham
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='gm677g$3io$2@ger.gmane.org' \
--to=heipei@hackvalue.de \
--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).