From: Michel <dae...@st...> - 2000-11-22 11:10:37
|
Alan Buxey wrote: > Hopefully the CVS update of the mol-branch was successful!! The update yes, but you obviously haven't committed yet (no commit message). > changes are to the following files: > > M 2.2/arch/ppc/config.in What changes have you made here? AFAIR I already re-enabled the configuration option when I started mol-branch? Before committing, please double-check that you are in fact working with mol-branch. > M 2.2/arch/ppc/kernel/head.S > M 2.2/arch/ppc/kernel/ppc_ksyms.c > M 2.2/arch/ppc/mm/init.c These are your local modifications, meaning your tree differs from the repository. > I guess that people who want to work on this will need to keep two > directories....one for the working 2.2, and one for the mol-branch 2.2 > > - otherwise, how do you keep gcc compiling the clean , or mol-branch > sources??? I guess i am correct? In principle yes, but there are various ways to overcome that issue. > One last thing....if you can see the problem, but cant use CVS (and > believe me, the use of branches etc can be confusing!!) then please just > email me the patches or snippets of code directly!! I'll be able to place > them into the CVS branch straight away....lets not have any more delays > due to people having to climb steep learning development curves :-) > (dont worry Michel, I'll help anyone who WANTS to learn CVS/branches :-) ) My opinion is that if someone wants to deal with this low-level code in development, he should take the time to learn about using CVS branches. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |