Re: Best way to request code change

[Jim Lambert <JLambert@Futurex.com>]

Thanks all for the help with this issue.  I was aware of the bugs@ and
sendbug process but didn't think it was the way to request new board
support.  Thanks again for the quick responses.

Jim

-----Original Message-----
From: Peter Hessler [mailto:phessler@theapt.org]
Sent: Friday, August 29, 2003 6:41 PM
To: Jim Lambert
Cc: 'misc@openbsd.org'
Subject: Re: Best way to request code change


tech@, or bugs@  (it doesn't work on your system, so it's a bug. ;-)

On Fri, 29 Aug 2003 16:06:52 -0700
Jim Lambert <JLambert@Futurex.com> wrote:

:I had looked at that page but I'm still not clear on exactly where to send
:the changes.  I didn't see any of the mailing lists that have a description
:indicating they would be a good place to submit diffs.  The CVS Changes
:mailing list looks like it is only for receiving notification of changes.
:The CTM list looks like it is used only for getting periodic small updates
:to the source instead of having to download large updates.  
:
:Any other advice would be appreciated.
:
:Jim
:
:-----Original Message-----
:From: Peter Hessler [mailto:phessler@theapt.org]
:Sent: Friday, August 29, 2003 6:00 PM
:To: Jim Lambert
:Cc: 'misc@openbsd.org'
:Subject: Re: Best way to request code change
:
:
:Submit diffs.  Look at http://openbsd.org/mail.html, there are several
:places you can send them.
:
:On Fri, 29 Aug 2003 15:20:06 -0700
:Jim Lambert <JLambert@Futurex.com> wrote:
:/snip/
::
::How would I go about making sure that these changes were put into the next
::release so I wouldn't have to download code and rebuild the kernel?
::
::TIA,
::
::Jim
::
::
:
:
:-- 
:I'm going to live forever, or die trying!
:		-- Spider Robinson
:
:


-- 
When you have to kill a man it costs nothing to be polite.
		-- Winston Churchill, On formal declarations of war