Re: git tree

Re: git tree

[Grant Likely]

On 4/16/07, Wolfgang Reissnegger <wolfgang.reissnegger@xilinx.com> wrote:
> Hi Grant,
>
> just checked out your virtex-dev branch. I noticed that you also have a
> virtex-temac and a virtex-sysace branch that got merged into the
> virtex-dev branch.
>
> I was wondering what your branching strategy is. How is your workflow
> if, say a TEMAC bug is being fixed? Do you plan on removing the
> individual driver branches around? In which branches do you fix the
> bugs? What do you pull from where?

I haven't quite decided yet.  The -temac and -sysace branches are a
bit of an experiment.  I thought it might be a good idea to maintain
the drivers in seperate branches so it is easy to get a diff on just
that driver; but the individual drivers are pretty seperate anyway (in
different directories).  I think I'll probably drop the -temac and
-sysace branches, and just maintain all my changes in the -dev branch.
 The -forupstream branch is specifically for patches that are due to
go upstream.  I'll add patches there when I think they are suitable
for mainline, and post them to the list.

>
> Do you pull changes from mainline back into your tree(s) on a daily basis?

No.  I'll rebase them once in a while as needed, but I'm not going to
try to stay perpetually up-to-date. The best way to get perpetual
up-to-dateness is to get the drivers iinto a good state and get them
into mainline (which is certainly my goal)

>
> Right now I branched off a 2.6.20 branch and then added my patches (e.g.
> uc0, mb). For each patch I created a new branch. Once I finished adding
> the patches, I consolidated everything into a "Xilinx" branch. I'm
> beginning to wonder if this was a good way to do it. My branches look
> like this now:
>
> * 2.6.20-xlnx
>   b2.6.20
>   b2.6.20-uc0
>   b2.6.20-uc0-mb
>   b2.6.20-uc0-mb-xlnx
>   master
>   origin
>
> Is it common practice to keep individual branches in the repository?

In public trees, no, not really.  In my private tree I've got task
branches galore, but it's probably too confusing to have loads of
branches in a public tree.

>
> I like the way you have the branches separated out for each driver. I
> think I should get them from your tree, merge them with what I have and
> add new driver branches as I add more drivers. This way it would be
> easiest to sync your tree with Xilinx's

As I said, the drivers are already split out by directories; so what I
did is probably unnecessary.  But, yes, feel free to pull my tree into
yours.

Cheers,
g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

Re: git tree

[David H. Lynch Jr]

Grant Likely wrote:
> I haven't quite decided yet.  The -temac and -sysace branches are a
> bit of an experiment.  I thought it might be a good idea to maintain
> the drivers in seperate branches so it is easy to get a diff on just
> that driver; but the individual drivers are pretty seperate anyway (in
> different directories).  I think I'll probably drop the -temac and
> -sysace branches, and just maintain all my changes in the -dev branch.
>  The -forupstream branch is specifically for patches that are due to
> go upstream.  I'll add patches there when I think they are suitable
> for mainline, and post them to the list.
    I would greatly appreciate pointers to so reference for using git
for kernel development.
    I have looked through most of the howto's and have a basic
competence with git.

    I am looking for something more like how to manage development with
possibly multiple
    devices/projects.
    Not necescarily what is possible, but what Standard Operating
Procedure for most developers.


   



-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.

"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein

Re: git tree

[Grant Likely]

On 4/21/07, David H. Lynch Jr <dhlii@comcast.net> wrote:
>     I am looking for something more like how to manage development with
> possibly multiple
>     devices/projects.
>     Not necescarily what is possible, but what Standard Operating
> Procedure for most developers.

The papers on http://www.jdl.com are very good at covering
collaboration with git.  Take a look at them, and then feel free to
ask more questions.

Cheers,
g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195