Git workflow for corporate Linux kernel development -


I work for a company that creates embedded systems using Linux Historically, we have always used CVS to store our kernel work.

  • Drivers for our proprietary hardware
  • Random Fixes for Linux bits which we use
  • Non-proprietary hardware drivers
  • To prepare Linux for our application, random yukky hacks
  • We are at that stage where we want to leak out some of our old corners on new versions, depending on the changes our To decide the old CVS workflow Psht like git.

    I am struggling to come up with a sensible workflow. I have exported our CVS repository for one of our kernels and there is a collection of changes over the appropriate base linus kernel. Where do I go from here?

    I have a central store that wants to make changes to all the developers. Are we safe to use Rebecca to pursue new base kernel modifications to carry forward the collection of new changes and Then will our development be taken to the top of the new central branch?

    Bonus points for getting workflows which we can easily separate changes that may be appropriate for upstream. I've been fed up with small (or small) amounts of useful changes all the time.

    Rebecca is good in one's local branch, provided that no one is pushing the local branch (since The history of that local branch has been rewritten). See for example.

    A dedicated "public" branch (which means it should be pushed) should be dedicated to developers GIT repositories, so that relevant changes can be suppressed.
    Possible, many if necessary, public branches may be together to maintain / fix a kernel version.

    A central repository can be set to integrate (i.e. pulled) into all the developer's branches.

    See more about merge workflows and publishing topics.


    Comments

    Popular posts from this blog

    c# - How to capture HTTP packet with SharpPcap -

    php - Multiple Select with Explode: only returns the word "Array" -

    php - jQuery AJAX Post not working -