tech-kern archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Newbie Kernel Programmer looking for first project.
Thanks for the help so far. Here is where I'm at.
When I see a pattern like this:
#idef DEBUG
printf("foo"...);
#endif
I replace those three line with
aprint_debug("foo...");
the reasoning being that aprint_debug uses AB_DEBUG to govern behavior,
and a new convention is replacing the old.
But I'm starting to question this. I see more complex preprocessor commands,
and now I wonder if I should just leave them alone. Could you give me some
feedback?
Michael Litchard
On 7/1/08, Jared D. McNeill <jmcneill%invisible.ca@localhost> wrote:
> Michael Litchard wrote:
>
> > I'm new to cvs, I know I should be using cvs to modify
> > the kernel source but I've never used it before.
> > Could someone point me to a tutorial
> > for cvs for the way the netbsd project uses it?
> > I know I need to do the following
> > download the source (done, using anoncvs)
> > start modifying the source (cvs is used here somehow?)
> >
>
> Just modify the file, no cvs commands necessary.
>
>
> > make a diff
> >
>
> cvs diff -u filename
>
>
> > open a pr with the diff.
> >
>
> send-pr, use your favourite $EDITOR to import the diff into the problem
> report template.
>
> Cheers,
> Jared
>
Home |
Main Index |
Thread Index |
Old Index