Re: How to use git for Linux kernel development ?

On Wed, Feb 01, 2006 at 12:38:44PM +0100, Laurent Pinchart wrote:

I have no idea how to layout my git repository to work on day-to-day 
development. I need to :

- commit bug fixes, external patches and internal modifications to a branch 
(or possibly on separate branches depending on what I commit if needed). The 
work will be based on Linux kernel 2.6.15 but I'd like to stay up-to-date 
with the master repository as much as possible.
- push bug fixes upstream by creating a patchset and submitting it by email.
- pull changes from upstream and merge them in my various branches when the 
upstream versions become stable enough.
- keep branches for all the versions shipped to the customers for bug fixes.

I'm the only developer working on the Linux kernel in my company, but that 
might change in a few months, so other developers will need to use git as 
well.

Is git able to accomodate my needs ?

Those certainly sound like the kinds of things it's meant for.

I've been trying to setup a git repository with a few branches over
the last two days, but I always had to throw everything away and start
back from zero. I haven't been able to figure out which branches I
should create and how I should use them.

Maybe you could be more specific about the problems you've had?

--b.