head	1.4;
access;
symbols;
locks; strict;
comment	@# @;


1.4
date	2001.03.16.22.03.38;	author lori;	state dead;
branches;
next	1.3;

1.3
date	2001.02.11.18.29.47;	author jrobbins;	state Exp;
branches;
next	1.2;

1.2
date	2001.02.09.00.59.20;	author susank;	state Exp;
branches;
next	1.1;

1.1
date	2001.01.29.19.47.05;	author lori;	state Exp;
branches;
next	;


desc
@@


1.4
log
@replaced by contributing_patches.html
@
text
@<HTML>
<HEAD>

<TITLE>Contributing Patches</TITLE>

</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <span class="Header" nowrap>Contributing Patches</span>
  
    <span class="PlainText"> 
     <P>Well-described, easy-to-apply patches are a pleasure for other developers to encounter and go a long way towards making the module or component IDE more stable and powerful.

     <P><SPAN class=PlainTextBold><I>If you are not yet a member of an open source project</I></SPAN> on this site but you have mailing list access, you can post a message about your proposed patch to the project's developer mailing list. (Read more about <A HREF="Subscribing.html">subscribing to project mailing lists</A>.)</P>

     <P><SPAN class=PlainTextBold><I>If you are a project member</I></SPAN>, first conduct a query of the project's issue database to determine whether this patch is associated with an already reported defect. 

     <P>If your patch pertains to an existing issue, you should use the <SPAN class=PlainTextBold>File Attach</SPAN> field in the issue edit screen to submit your patch and the <SPAN class=PlainTextBold>Add Comment</SPAN> section to post an explanatory message. (Remember that changes to issues generate automatic email messages to the issue's owner and anyone on the cc list. All of those people will receive your message and a link to your patch.)
     <P>If an issue <I>does not exist</I>, submit your patch as a new issue, using the <I>Patch</I> link in the "Enter An Issue" section of the <B>Project Issues</B> page. Attach your patch file to the new issue. Here's how to do it:</P>
     <UL>    
  <LI>First, make sure you are making changes in the most recent version of the source files -- for this, it is best to use CVS to check out the source (on the CVS trunk), make your modifications (but do not check them in), and then run the command: </P>
<P>
<span class="TypewriterBold">cvs diff -c > mypatch</SPAN>
<P>
... to get a context-format patch for the sources. This gives you a patch file which includes information about the version you are patching, the filenames, and the contents of the change. This is the preferred way to keep track of patches and makes it easier for others to find and test your patch.
     <P>
<LI>To apply a patch, go to the proper directory and run: 
<P>
<span class="TypewriterBold">patch &lt; issuepatch.diff</span>
<P>

<LI>Always include a message with your patch with the following information:
     <UL>

      <LI>A description of what problem or defect you are attempting to fix, and the steps to reproduce it, if possible.

      <LI>A description of what the behavior should be with the patch in place. 

      <LI>A description of how the patch works, if reasonable. If a significant amount of code is involved, include within the message that you agree to let the patch be used under the applicable project license as part of the IDE's code.
     </UL>
  </UL>
     <P>The developer responsible for the section of code affected should either apply the patch and mark the defect (if there is one registered) as fixed, or reply with an objection if it does not seem safe, does not appear to fix the problem, or there is not really a problem to begin with. Notifications of any changes to the issues database, as well as CVS check-ins, are automatically sent to the appropriate issue assignee/cc'd and CVS mailing lists, so you can monitor whether the patch has been applied. Be sure to subscribe to at least the CVS and issue mailing lists for the module you are working on.</P>

     <P>If you do not know exactly how to fix a problem, but have an idea about what is causing it, you can post a message about this on the developer discussion list for other project members' suggestions or to find someone who knows how to fix it.</P>


<HR NOSHADE SIZE=1>
<A HREF="ProjectIssues.html">Back to Project Issues help</A><BR>
<A HREF="Help.html">Back to main Help index</A>
    </SPAN>
  </TR>
</TABLE>


</BODY>
</HTML>
@


1.3
log
@added <title> tags to all files
@
text
@@


1.2
log
@removed window's nasty line breaks, and corrected more links in HelpBox files
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d1 7
d56 2
@


1.1
log
@new and revised help documentation for v1.0
@
text
@d1 48
a48 48
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <span class="Header" nowrap>Contributing Patches</span>
  
    <span class="PlainText"> 
     <P>Well-described, easy-to-apply patches are a pleasure for other developers to encounter and go a long way towards making the module or component IDE more stable and powerful.

     <P><SPAN class=PlainTextBold><I>If you are not yet a member of an open source project</I></SPAN> on this site but you have mailing list access, you can post a message about your proposed patch to the project's developer mailing list. (Read more about <A HREF="Subscribing.html">subscribing to project mailing lists</A>.)</P>

     <P><SPAN class=PlainTextBold><I>If you are a project member</I></SPAN>, first conduct a query of the project's issue database to determine whether this patch is associated with an already reported defect. 

     <P>If your patch pertains to an existing issue, you should use the <SPAN class=PlainTextBold>File Attach</SPAN> field in the issue edit screen to submit your patch and the <SPAN class=PlainTextBold>Add Comment</SPAN> section to post an explanatory message. (Remember that changes to issues generate automatic email messages to the issue's owner and anyone on the cc list. All of those people will receive your message and a link to your patch.)
     <P>If an issue <I>does not exist</I>, submit your patch as a new issue, using the <I>Patch</I> link in the "Enter An Issue" section of the <B>Project Issues</B> page. Attach your patch file to the new issue. Here's how to do it:</P>
     <UL>    
  <LI>First, make sure you are making changes in the most recent version of the source files -- for this, it is best to use CVS to check out the source (on the CVS trunk), make your modifications (but do not check them in), and then run the command: </P>
<P>
<span class="TypewriterBold">cvs diff -c > mypatch</SPAN>
<P>
... to get a context-format patch for the sources. This gives you a patch file which includes information about the version you are patching, the filenames, and the contents of the change. This is the preferred way to keep track of patches and makes it easier for others to find and test your patch.
     <P>
<LI>To apply a patch, go to the proper directory and run: 
<P>
<span class="TypewriterBold">patch &lt; issuepatch.diff</span>
<P>

<LI>Always include a message with your patch with the following information:
     <UL>

      <LI>A description of what problem or defect you are attempting to fix, and the steps to reproduce it, if possible.

      <LI>A description of what the behavior should be with the patch in place. 

      <LI>A description of how the patch works, if reasonable. If a significant amount of code is involved, include within the message that you agree to let the patch be used under the applicable project license as part of the IDE's code.
     </UL>
  </UL>
     <P>The developer responsible for the section of code affected should either apply the patch and mark the defect (if there is one registered) as fixed, or reply with an objection if it does not seem safe, does not appear to fix the problem, or there is not really a problem to begin with. Notifications of any changes to the issues database, as well as CVS check-ins, are automatically sent to the appropriate issue assignee/cc'd and CVS mailing lists, so you can monitor whether the patch has been applied. Be sure to subscribe to at least the CVS and issue mailing lists for the module you are working on.</P>

     <P>If you do not know exactly how to fix a problem, but have an idea about what is causing it, you can post a message about this on the developer discussion list for other project members' suggestions or to find someone who knows how to fix it.</P>


<HR NOSHADE SIZE=1>
<A HREF="ProjectIssues.html">Back to Project Issues help</A><BR>
<A HREF="Help.html">Back to main Help index</A>
    </SPAN>
  </TR>
</TABLE>


@

