[geeklog-users] submitting code

Lucas Gonze lgonze at panix.com
Mon Dec 15 19:30:46 EST 2003


Ok, thanks Blaine.

- Lucas

On Monday, Dec 15, 2003, at 19:24 America/New_York, Blaine Lang wrote:


> Thats great that you are submitting a recommended fix with your bug

> reports.

> You can safely include the code inline or as an attachment when

> submitting

> your bug. This way everything is online and you can track it as well

> -- easy

> to get lost in emails otherwise.

>

> Thanks for your ideas and feedback.

>

> Regards,

> Blaine

> ----- Original Message -----

> From: "Lucas Gonze" <lgonze at panix.com>

> To: <geeklog-users at lists.geeklog.net>

> Sent: Monday, December 15, 2003 7:12 PM

> Subject: Re: [geeklog-users] submitting code

>

>

>> In general, I never report bugs without also submitting a fix, so

>> that's really what my question is about. So far there are have been a

>> fix in search.php, one in the email address check, one in COM_refresh,

>> and one in the code to email the password. Any suggestions for how I

>> can do that in a way which is more likely to be successful?

>>

>> - Lucas

>>

>> On Monday, Dec 15, 2003, at 18:56 America/New_York, Blaine Lang wrote:

>>

>>> I don't think that project owners ignore patches and bug reports. We

>>> do

>>> appreciate a little patience and ask that bugs be reported.

>>> Many times, the developer may already be aware or working on a future

>>> release. Critical security related problems get priority and

>>> attention.

>>>

>>> If you have a Core Geeklog bug - then report it using the Link of the

>>> main

>>> page on geeklog.net (Top Left)

>>>

>>> Like many others, I have a number of projects and many more ideas

>>> then

>>> time.

>>> Depending on the issue, I proritize them and the project.

>>>

>>> Regards,

>>> Blaine

>>> ----- Original Message -----

>>> From: "Lucas Gonze" <lgonze at panix.com>

>>> To: <geeklog-users at lists.geeklog.net>

>>> Sent: Monday, December 15, 2003 5:57 PM

>>> Subject: [geeklog-users] submitting code

>>>

>>>

>>>> Ok, given that the project maintainers always ignore patches, I'm

>>>> wondering what other users do with their code. Does anybody else

>>>> submit stuff, or do you just keep a private fork on your own

>>>> machine?

>>>> Any advice?

>>>>

>>>>

>>>>

>>>> _______________________________________________

>>>> geeklog-users mailing list

>>>> geeklog-users at lists.geeklog.net

>>>> http://lists.geeklog.net/listinfo/geeklog-users

>>>

>>> _______________________________________________

>>> geeklog-users mailing list

>>> geeklog-users at lists.geeklog.net

>>> http://lists.geeklog.net/listinfo/geeklog-users

>>>

>>

>> _______________________________________________

>> geeklog-users mailing list

>> geeklog-users at lists.geeklog.net

>> http://lists.geeklog.net/listinfo/geeklog-users

>

> _______________________________________________

> geeklog-users mailing list

> geeklog-users at lists.geeklog.net

> http://lists.geeklog.net/listinfo/geeklog-users

>





More information about the geeklog-users mailing list