Re: Diff`s for MOL

[Alan B. <al...@ms...>]

hi,

> > Hopefully the CVS update of the mol-branch was successful!!
> 
> The update yes, but you obviously haven't committed yet (no commit message).

mea culpa.  ok, I am now committing.

> > 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.

i am treble double checking  :-)
(even *if* the docs say that the -r is sticky, i'm always using -r
mol-branch ! ;-) )

by the way, is this some CVS 'thing' or am i making an ooops, but to do a
commit i must use the full line: eg

cvs -d:ext:ala...@cv...:/cvsroot/linux-apus 
commit -r mol-branch 2.2/arch/ppc/mm/init.c  

because when i use the -d part as a CVSROOT, I get prompted for password,
but then when i do a plain 

cvs commit -r mol-branch 2.2/arch/ppc/mm/init.c  

i get told that theres no password.... 

> > 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.

and now they've been committed  :-)
 
> In principle yes, but there are various ways to overcome that issue.

more to learn ;-)
 
> 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.
               ^^

or she, one forever hopes!  okay, i can agree - what i can offer, then, is
some help to anyone wanting to learn  (though I'm still open to people
emailing me changes if it'll accelerate any progress 8-) )

alan