[Asterisk-Users] Re: [Asterisk-Dev] How to submit a patch?

[Rob Gagnon]

Oops.... The first part should have read "bugs.digium.com", not 
www.digium.com

All other information is correct.

----- Original Message ----- 
From: "Rob Gagnon" <rob at networkip.net>
To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
Sent: Thursday, October 28, 2004 6:39 PM
Subject: Re: [Asterisk-Users] Re: [Asterisk-Dev] How to submit a patch?


> See http://www.digium.com
>
> and look under the news about "Disclaimers"
>
> or here are two direct links:
>
> http://www.digium.com/disclaim.changes
> or
> http://www.digium.com/disclaimer.txt
>
> Either one works.
>
> fax to +1-256-864-0464 and/or snail mail to:
>
> Disclaimers
> Digium
> 150 West Park Loop Suite 100
> Huntsville, AL 35806
> USA
>
>
> ----- Original Message ----- 
> From: "Renato Mintz" <renatomintz at gmail.com>
> To: "Asterisk Users Mailing List - Non-Commercial Discussion" 
> <asterisk-users at lists.digium.com>
> Cc: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
> Sent: Thursday, October 28, 2004 4:49 PM
> Subject: Re: [Asterisk-Users] Re: [Asterisk-Dev] How to submit a patch?
>
>
>> Josh, please help me as I'm really naive to this process. Is there a
>> specific text you would like to see in the disclaimer? Where should I
>> send this disclaimer file to?
>>
>> Tks,
>>
>> Renato
>>
>>
>> On Mon, 25 Oct 2004 21:08:35 -0500, Josh Roberson
>> <twisted at indigent-networks.com> wrote:
>>> Just so everyone's clear on the patch submission etiquette here...
>>> (sorry for the crosspost, but I believe this is relevant to both
>>> users/dev lists)
>>>
>>> To submit a patch, PLEASE PLEASE PLEASE help us out by doing the 
>>> following:
>>>
>>> Search the bugtracker to see if someone has already submitted a
>>> patch/request/bug that may be relevant to your patch.  If so, please use
>>> the existing bug, and follow the relevant sections below.  If not,
>>> please follow the following guidelines:
>>>
>>> 1)  make sure you save your patch in a unified diff, based on
>>> stable/head cvs if possible.  (cvs diff -u path/to/file.c [within the
>>> asterisk source tree will keep you from having to have two copies of the
>>> source file, too]) and save it into a file ending in a .txt extension
>>> (for faster review by us bug marshals, and Mark.
>>>
>>> 2) make sure you add the header "[patch]" without quotes to the
>>> subject/summary field.  This will help us quickly identify your bug as a
>>> patch, and will once again, help speed up the process.
>>>
>>> 3) please refrain from using whitespaces instead of tabs within your
>>> patch, also, please try not to add any unnecessary whitespace.
>>>
>>> and last but not least
>>>
>>> 4) if you don't already have a disclaimer on file, please file one.
>>> Once filed, PLEASE mention somewhere in your bug that you have one on
>>> file.  This saves a lot of time, and has held back lots of good patches,
>>> because the powers that be have to ask, then wait on a response as to
>>> wether or not the patch has been properly disclaimed.
>>>
>>> Thanks for listening!
>>>
>> _______________________________________________
>> Asterisk-Dev mailing list
>> Asterisk-Dev at lists.digium.com
>> http://lists.digium.com/mailman/listinfo/asterisk-dev
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev