Re: [gcdb-devel] Hi

[Cory W. <gp...@ca...>]

I don't actively work on gcdb anymore, but I'll speak up, since the list
is usually very very quiet.

To send a patch, just send the diff file to the list, and explain what
the patch provides.  The best way is to try and seperate your patches by
features, not sending one giant patch that does alot of little jobs.

I'm glad to hear gcdb helps you out, keep letting us know how you are
working with it!

On Thu, 2001-11-29 at 17:26, Mike Eheler wrote:
> Just joined the list, and wanted to say hi.
> 
> I think you guys have a great thing going, this software has come closer 
> to matching our needs as a web hosting provider than any others.
> 
> Over the coming weeks or so, I will be making some changes to the code 
> on our end to tweak it a bit, to try and make it work more like the way 
> we want, and I will be in charge of development, and was hoping to be 
> able to submit a patch here or there.
> 
> I've never worked on an open source project before, and was kind of 
> wondering what the process is for submitting a patch?
> 
> Thanks,
>     Mike
> 
> 
> _______________________________________________
> gcdb-devel mailing list
> gcd...@li...
> https://lists.sourceforge.net/lists/listinfo/gcdb-devel
> 
-- 
Cory 'G' Watson

BOFH excuse #170:

popper unable to process jumbo kernel