CVS: tmda/htdocs bugs.ht, 1.8, 1.9 bugs.html, 1.45, 1.46 tmda-vdomains.ht, 1.4, 1.5 tmda-vdomains.html, 1.22, 1.23
"Jason R. Mastaler" <[email protected]>
| Newsgroups | gmane.mail.spam.tmda.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/tmda/tmda/htdocs In directory sc8-pr-cvs1:/tmp/cvs-serv405 Modified Files: bugs.ht bugs.html tmda-vdomains.ht tmda-vdomains.html Log Message: All correspondence related to TMDA 1.0.x belongs on tmda-users, not tmda-workers. Index: bugs.ht =================================================================== RCS file: /cvsroot/tmda/tmda/htdocs/bugs.ht,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- bugs.ht 12 Mar 2003 21:12:01 -0000 1.8 +++ bugs.ht 19 Dec 2003 20:34:58 -0000 1.9 @@ -5,9 +5,9 @@ things easier on the developers, please adhere to the following guidelines. <br><br> -Bug reports and patch submissions should be sent to the -<a href="http://tmda.net/lists/listinfo/tmda-workers" -TARGET="Resource Window">tmda-workers</a> mailing list. +Bug reports and patch submissions for TMDA 1.0.x should be sent to the +<a href="http://tmda.net/lists/listinfo/tmda-users" +TARGET="Resource Window">tmda-users</a> mailing list. You <strong>do not</strong> need to be subscribed to post a message there. <h4>Reporting Bugs:</h4> @@ -27,12 +27,7 @@ <ul> <li>Please make sure your patch works with the earliest supported -version of Python. See the <a href="requirements.html">requirements</a> -page for what we currently support. For example, if TMDA supports -Python 2.1 and above, you should test your changes with Python 2.1, -even if you normally use a more recent version of Python. If you plan -to contribute code on a frequent basis, you should get into the habit of using -the earliest supported Python for all of your TMDA development. +version of Python, which is Python 2.1.x. <br><br> <li>As far as preferred coding style, I try to follow the general @@ -53,46 +48,9 @@ When making patches with <strong>diff</strong>, please use the <b>-u</b> option, or if your diff doesn't support it, <b>-c</b>. Also, it is helpful if you create the patch from the top level of the TMDA source -directory: -<br><br> - -<li> -Diffs should be made against the current development source from CVS rather -than the particular TMDA release you happen to be using. -<br><br> +directory. </ul> -Here is an example illustrating some of the above concepts: - -<ol> - -<li>Checkout the latest developement sources from TMDA's CVS repository. -This will create a `tmda' subdirectory in your current working directory -containing the source: - -<blockquote><pre> -% cd /usr/local/src -% cvs -d:pserver:[email protected]:/cvsroot/tmda login -[press return at the password prompt] - -% cvs -z3 -d:pserver:[email protected]:/cvsroot/tmda co tmda -</blockquote></pre> - -<li>Make the necessary changes: - -<blockquote><pre> -% cd /usr/local/src/tmda -(hack, hack, hack....) -</blockquote></pre> - -<li>Create your patch called "tmda.diff": - -<blockquote><pre> -% cd /usr/local/src/tmda -% cvs diff -u > tmda.diff -</blockquote></pre> - -</ol> If you wish, accompany your patch with an update to the apropriate ChangeLog file. If you use Emacs, you can use the <em>M-x Index: bugs.html =================================================================== RCS file: /cvsroot/tmda/tmda/htdocs/bugs.html,v retrieving revision 1.45 retrieving revision 1.46 diff -u -r1.45 -r1.46 --- bugs.html 19 Dec 2003 20:13:15 -0000 1.45 +++ bugs.html 19 Dec 2003 20:35:00 -0000 1.46 @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Fri Dec 19 13:04:57 2003 --> +<!-- Fri Dec 19 13:30:59 2003 --> <!-- USING HT2HTML 2.0 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -208,9 +208,9 @@ things easier on the developers, please adhere to the following guidelines. <br><br> -Bug reports and patch submissions should be sent to the -<a href="http://tmda.net/lists/listinfo/tmda-workers" -TARGET="Resource Window">tmda-workers</a> mailing list. +Bug reports and patch submissions for TMDA 1.0.x should be sent to the +<a href="http://tmda.net/lists/listinfo/tmda-users" +TARGET="Resource Window">tmda-users</a> mailing list. You <strong>do not</strong> need to be subscribed to post a message there. <h4>Reporting Bugs:</h4> @@ -230,12 +230,7 @@ <ul> <li>Please make sure your patch works with the earliest supported -version of Python. See the <a href="requirements.html">requirements</a> -page for what we currently support. For example, if TMDA supports -Python 2.1 and above, you should test your changes with Python 2.1, -even if you normally use a more recent version of Python. If you plan -to contribute code on a frequent basis, you should get into the habit of using -the earliest supported Python for all of your TMDA development. +version of Python, which is Python 2.1.x. <br><br> <li>As far as preferred coding style, I try to follow the general @@ -256,46 +251,9 @@ When making patches with <strong>diff</strong>, please use the <b>-u</b> option, or if your diff doesn't support it, <b>-c</b>. Also, it is helpful if you create the patch from the top level of the TMDA source -directory: -<br><br> - -<li> -Diffs should be made against the current development source from CVS rather -than the particular TMDA release you happen to be using. -<br><br> +directory. </ul> -Here is an example illustrating some of the above concepts: - -<ol> - -<li>Checkout the latest developement sources from TMDA's CVS repository. -This will create a `tmda' subdirectory in your current working directory -containing the source: - -<blockquote><pre> -% cd /usr/local/src -% cvs -d:pserver:[email protected]:/cvsroot/tmda login -[press return at the password prompt] - -% cvs -z3 -d:pserver:[email protected]:/cvsroot/tmda co tmda -</blockquote></pre> - -<li>Make the necessary changes: - -<blockquote><pre> -% cd /usr/local/src/tmda -(hack, hack, hack....) -</blockquote></pre> - -<li>Create your patch called "tmda.diff": - -<blockquote><pre> -% cd /usr/local/src/tmda -% cvs diff -u > tmda.diff -</blockquote></pre> - -</ol> If you wish, accompany your patch with an update to the apropriate ChangeLog file. If you use Emacs, you can use the <em>M-x Index: tmda-vdomains.ht =================================================================== RCS file: /cvsroot/tmda/tmda/htdocs/tmda-vdomains.ht,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- tmda-vdomains.ht 5 Jul 2003 00:27:37 -0000 1.4 +++ tmda-vdomains.ht 19 Dec 2003 20:35:02 -0000 1.5 @@ -276,11 +276,6 @@ with a 'bare' From: field and will tag the envelope sender with a dated address so that bounces do not get stuck in the pending queue. -<p> - -Please report any problems with the VPopMail support to the [email protected] mailing list. - <h2><a name="vmailmgr">VMailMgr</a></h2> Since each virtual domain is under the control of a different system @@ -369,7 +364,3 @@ with a 'bare' From: field and will tag the envelope sender with a dated address so that bounces do not get stuck in the pending queue. -<p> - -Please report any problems with the VMailMgr support to the [email protected] mailing list. Index: tmda-vdomains.html =================================================================== RCS file: /cvsroot/tmda/tmda/htdocs/tmda-vdomains.html,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- tmda-vdomains.html 19 Dec 2003 20:13:15 -0000 1.22 +++ tmda-vdomains.html 19 Dec 2003 20:35:02 -0000 1.23 @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Fri Dec 19 13:05:06 2003 --> +<!-- Fri Dec 19 13:32:52 2003 --> <!-- USING HT2HTML 2.0 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -479,11 +479,6 @@ with a 'bare' From: field and will tag the envelope sender with a dated address so that bounces do not get stuck in the pending queue. -<p> - -Please report any problems with the VPopMail support to the [email protected] mailing list. - <h2><a name="vmailmgr">VMailMgr</a></h2> Since each virtual domain is under the control of a different system @@ -572,10 +567,6 @@ with a 'bare' From: field and will tag the envelope sender with a dated address so that bounces do not get stuck in the pending queue. -<p> - -Please report any problems with the VMailMgr support to the [email protected] mailing list. </td><!-- end of body cell --> </tr><!-- end of sidebar/body row -->