[Slashem-devel] Re: [Slashem-discuss] Questions about fixing bugs

[J. A. H. <al...@ju...>]

On 2004.09.14 14:53 Andy Ruse wrote:
> Hi,
> 
> Looking through the bugs listing on Sourceforge, I noticed that many of
> the bugs are probably within my ability to fix.  So, I want to go ahead 
> and fix them.

Excellent.

> I've never used CVS before.  I managed to download the current
> CVS source for Slash'em and then I fixed a simple bug.  Now, what's the 
> procedure for producing a diff patch of the correct format?  I noticed 
> on the slashem-checkins mailing list that patches only cover one file at 
> a time.  Can I check patches into CVS myself, or do I need to
> submit them to someone with higher priveleges?

The patches on the slashem-checkins mailing list are auto-generated and
cover one directory at a time (which often does mean one file in practice).
When producing patches manually it's actually better to keep all the
changes in one place. If you have made changes in your local cvs tree
then you can generate a suitable patch by changing directory to the top
pf the cvs tree and doing:

% cvs -Q diff -Nau > xxx.patch

The patch can then be attached to the bug report for review. It's probably
sensible to drop a note to slashem-devel as well just in case your patch
is missed.

> I've never dealt with a project as complex as Slash'em.  Does anybody 
> have any tips to help me comprehend how all this source code works 
> together?

There are some very incomplete notes in doc/sources.txt which might
provide some limited help.

Cheers,

-- 
J. Ali Harlow
al...@ju...