[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] CVS of development work



Hi Richard,

Richard Klosinski wrote:
> I would like to put certain parts of the uClinux package under cvs 
> control, specifically those pertaining to the microblaze. Its hard to 
> find all the directories things are hidden in, but I think I figured it 
> out. So far, I have:
> 
> uClinux-2.4.x/arch/microblaze
> 
> uClinux-2.4.x/include/asm-microblaze
> 
> uClinux-dist/vendors/Insight

That's the vast majority of it - there may be others, for example if you 
need to create or modify device drivers to suite your platform, 
uClinux-2.4.x/drivers/...

If you have flash memory and need to create a custom MTD map, that will 
be in uClinux-2.4.x/drivers/mtd/maps

> Can anyone think of others I should be saving. I will be porting 
> mbvanilla to a nuhorizon sp3 platform, and I want to keep track of my 
> changes (its easy to break something).

Co-mingling source sub-trees from two different CVS repositories can get 
a bit clumsy, particularly when it comes to merging the changes back 
into the mainline.  I tend to just use parallel local copies of the 
tree, snapshotting at critical points, then when something works, fold 
it into the public CVS as quickly as possible.

The advice to me long ago was "submit early and submit often"!  I have 
commit rights now, and I try to get submissions in there as quickly as 
possible (don't always achieve it, but anyway ;)  As long as it doesn't 
break any existing platforms (I look after mbvanilla_net, Yashi watches 
suzaku) then it can usually go straight in.

Regards,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/