[gs-cvs] rev 8024 - trunk/gs/doc
giles at ghostscript.com
giles at ghostscript.com
Tue Jun 5 16:08:50 PDT 2007
Author: giles
Date: 2007-06-05 16:08:49 -0700 (Tue, 05 Jun 2007)
New Revision: 8024
Removed:
trunk/gs/doc/Maintain.htm
Modified:
trunk/gs/doc/Develop.htm
trunk/gs/doc/Issues.htm
trunk/gs/doc/Make.htm
trunk/gs/doc/Projects.htm
trunk/gs/doc/Readme.htm
trunk/gs/doc/Testing.htm
trunk/gs/doc/Use.htm
Log:
Remove additional artofcode references and the obsolete Maintain.htm.
Modified: trunk/gs/doc/Develop.htm
===================================================================
--- trunk/gs/doc/Develop.htm 2007-06-05 23:04:12 UTC (rev 8023)
+++ trunk/gs/doc/Develop.htm 2007-06-05 23:08:49 UTC (rev 8024)
@@ -140,8 +140,7 @@
<!-- [1.3 begin hint] ====================================================== -->
<p>For other information, see the <a href="Readme.htm">Ghostscript
-overview</a> and the documentation related to <a
-href="Maintain.htm">maintaining Ghostscript</a>.
+overview</a>.
<!-- [1.3 end hint] ======================================================== -->
Modified: trunk/gs/doc/Issues.htm
===================================================================
--- trunk/gs/doc/Issues.htm 2007-06-05 23:04:12 UTC (rev 8023)
+++ trunk/gs/doc/Issues.htm 2007-06-05 23:08:49 UTC (rev 8024)
@@ -48,7 +48,7 @@
have enough resources. These may or may not be addressed in future releases.
<p>
If you would like to take responsibility for any of these issues, please
-<a href="mailto:raph at artofcode.com">contact us</a>.
+<a href="mailto:info at artifex.com">contact us</a>.
<p>
Additional comments on implementation approaches or project goals are in
<I>italic type like this</I>.
Deleted: trunk/gs/doc/Maintain.htm
===================================================================
--- trunk/gs/doc/Maintain.htm 2007-06-05 23:04:12 UTC (rev 8023)
+++ trunk/gs/doc/Maintain.htm 2007-06-05 23:08:49 UTC (rev 8024)
@@ -1,228 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<title>AFPL Ghostscript maintenance procedures</title>
-<!-- $Id$ -->
-<link rel="stylesheet" type="text/css" href="gs.css" title="Ghostscript Style">
-</head>
-
-<body>
-<!-- [1.0 begin visible header] ============================================ -->
-
-<!-- [1.1 begin headline] ================================================== -->
-
-<h1>AFPL Ghostscript maintenance procedures</h1>
-
-<!-- [1.1 end headline] ==================================================== -->
-
-<!-- [1.2 begin table of contents] ========================================= -->
-
-<h2>Table of contents</h2>
-
-<blockquote><ul>
-<li><a href="#Introduction">Introduction</a>
-<li><a href="#Problem_reporting">Problem reporting</a>
-<ul>
-<li><a href="#Uploading_test_data">Uploading test data</a>
-</ul>
-<li><a href="#CVS">Rules for CVS commits</a>
-<li><a href="#Adding_or_removing_files">Adding or Removing Files</a>
-</ul></blockquote>
-
-<!-- [1.2 end table of contents] =========================================== -->
-
-<!-- [1.3 begin hint] ====================================================== -->
-
-<p>For other information, see the <a href="Readme.htm">Ghostscript
-overview</a> and the instructions on how to <a href="Make.htm">build
-Ghostscript</a>.
-
-<!-- [1.3 end hint] ======================================================== -->
-
-<hr>
-
-<!-- [1.0 end visible header] ============================================== -->
-
-<!-- [2.0 begin contents] ================================================== -->
-
-<h2><a name="Introduction"></a>Introduction</h2>
-
-<p>
-This document describes various maintenance procedures associated with AFPL
-Ghostscript. It is only meant for developers actively working on AFPL
-Ghostscript; some parts of it are only relevant to developers who have
-commit access to the source repository.
-
-<hr>
-
-<h2><a name="Problem_reporting"></a>Problem reporting</h2>
-
-<h3><a name="#Uploading_test_data"></a>Uploading test data</h3>
-
-<p>
-If a test file can't be attached to the report in the public
-bug tracking system, put it in <tt>casper:/home/support/<bug number>/</tt>.
-This is a good place to collect test files of all kinds.
-
-<hr>
-
-<h2><a name="CVS"></a>Rules for CVS Commits</h2>
-
-<p>
-The primary repository for Ghostscript code is
-<a href="http://cvs.ghostscript.com" class="offsite">cvs.ghostscript.com</a>
-This section describes a few rules intended to make life easier
-for people working with this code base.
-
-<p>
-At any given time, there are usually two active branches: a stable
-branch and a development branch. The development branch is HEAD, which
-is the default when doing a checkout without a -r flag. The stable
-branch is tagged after the previous major release. For example:
-GS_8_0x, GS_7_0x, GS_6_5.
-
-<p>
-A concise and useful document for working with CVS branches is Jeff
-Semke's <a href="http://www.psc.edu/~semke/cvs_branches.html"
-class="offsite">CVS
-Branch and Tag Primer</a>. A
-somewhat more detailed explanation is the <a
-href="http://www.loria.fr/~molli/cvs/doc/cvs_5.html"
-class="offsite">Branching and
-merging</a> section from the CVS documentation by Pascal Molli.
-
-<p>
-For new development commits, you can basically ignore the
-branches. Just commit to the HEAD branch. For bug fixes for the stable
-branch, it is your responsibility to commit to both the stable branch
-and, if appropriate, HEAD.
-
-<p>
-When modifying a number of files for a single issue, please group them
-together as a single commit. For two separate sets of changes dealing
-with two different issues, there should be two commits.
-
-<p>
-You should strive not to introduce any new bugs with your
-commit. Always make sure the code compiles before committing. Test the
-changes with several files, including the problem file in the case of
-a bug fix, and other files that may have been affected by the
-changes.
-
-<p>
-Always supply a descriptive log message for your commits. These log
-messages are used to automatically generate the <a
-href="News.htm">News.htm</a> file and History changelogs, and are also
-crucial for navigating the change history. Please try to
-keep the style of the descriptions similar to those in the current
-History#.htm files.
-
-<p>
-Log messages beginning with 'Fix' are treated specially. Such messages are
-put under the "Fixes problems" heading when the History files are
-generated. Additionally, if the first four characters are 'Fix:' this is removed
-(i.e., "Fix: The xyz" becomes "The xyz", but "Fixes xyz" is copied unchanged).
-This feature is intended for explicit bugfixes and should be avoided for
-enhancements or commits with long explanations.
-
-<p>
-Information about who changed what, when, and why is maintained in the
-CVS logs. In general, a file should be a clean representation of the
-current version rather than a history trail of how it got
-there. Keeping old code around for reference is usually not necessary,
-as it is stored in the CVS diffs. When necessary, use #if / #endif, or
-descriptive conditionals such as #ifdef OLD_CMAP_TABLES. Do not
-comment out old code. (A very few files that are distributed separate
-from Ghostscript have a change log at the beginning, which should be
-maintained: currently, only ansiknr.c and md5.[ch].)
-
-<p>
-Additionally, if your patch removes a feature, changes an interface or
-otherwise creates an incompatibility with the last release, you
-must add an entry to the "Incompatible changes" section of <tt>News.htm</tt>
-as this information can only be generated manually.
-This admonition applies to api changes that might
-affect other developers as well as user issues like switch behavior.
-Upon release, the accumulated incompatible changes will be moved to the
-relevant History file, and the News collection in cvs will be wiped clean
-for the next version.
-
-<p>
-All patches should be reviewed before being committed. Please email your
-patch to <a
-href="mailto:gs-code-review at ghostscript.com">gs-code-review at ghostscript.com</a>.
-Make sure to include your commit comment and any other information
-that would be helpful for the review. Also, please identify which
-branches the patch is intended for. The code review list is also
-a good place to put extensive documentation on changes (motivation and
-associated reasoning for example) that are too verbose for the cvs
-changelog.
-
-<p>
-If you are not an employee or consultant of Artifex or artofcode, then
-we need a copyright assignment form so we can incorporate your
-changes. Please email Raph Levien <<a
-href="mailto:raph at artofcode.com">raph at artofcode.com</a>> and
-include your snailmail address for a hardcopy assignment form.
-
-<h2><a name="Adding_or_removing_files"></a>Adding or removing files</h2>
-
-<p>
-When adding or removing files, don't forget to invoke <b><tt>cvs
-add</tt></b> or <b><tt>cvs rm</tt></b>.
-
-<p>
-When adding files, update the file roadmap in
-<b><tt>doc/Develop.htm</tt></b>.
-
-<p>
-When adding or removing files other than .c or .h: If the files will be
-used at runtime, check the install list in <b><tt>unixinst.mak</tt></b>.
-
-<p>
-When adding .c files, update the relevant <b><tt>.mak</tt></b> file
-(usually <b><tt>devs.mak</tt></b>, <b><tt>int.mak</tt></b>, or
-<b><tt>lib.mak</tt></b>).
-
-<p>
-When adding new documentation, add a link to <tt>doc/Readme.htm</tt> and
-a short blurb describing the contents of the file.
-
-<p>
-When adding or changing fonts, update <b><tt>lib/Fontmap.GS</tt></b>,
-<b><tt>fonts.mak</tt></b>, and possibly the compiled fonts in
-<b><tt>gs.mak</tt></b> and the examples in
-<b><tt>doc/Fonts.htm</tt></b>.
-
-<p>
-When adding .ps files, update <b><tt>doc/Psfiles.htm</tt></b>.
-
-<p>
-Likewise, you will want to delete any references for a file you
-remove from Ghostscript.
-
-<!-- [2.0 end contents] ==================================================== -->
-
-<!-- [3.0 begin visible trailer] =========================================== -->
-<hr>
-
-<p>
-<small>Copyright © 2000-2006 Artifex Software, Inc. All rights reserved.</small>
-
-<p>
-This software is provided AS-IS with no warranty, either express or
-implied.
-
-This software is distributed under license and may not be copied, modified
-or distributed except as expressly authorized under the terms of that
-license. Refer to licensing information at http://www.artifex.com/
-or contact Artifex Software, Inc., 7 Mt. Lassen Drive - Suite A-134,
-San Rafael, CA 94903, U.S.A., +1(415)492-9861, for further information.
-
-<p>
-<small>Ghostscript version 8.57, 11 May 2007
-
-<!-- [3.0 end visible trailer] ============================================= -->
-
-</body>
-</html>
Modified: trunk/gs/doc/Make.htm
===================================================================
--- trunk/gs/doc/Make.htm 2007-06-05 23:04:12 UTC (rev 8023)
+++ trunk/gs/doc/Make.htm 2007-06-05 23:08:49 UTC (rev 8024)
@@ -874,8 +874,8 @@
If you have comments or questions about this situation, please feel free to
contact the Free Software Foundation, authors of the GPL and copyright
holders of GNU readline, at <a href="mailto:gnu at gnu.org">gnu at gnu.org</a>,
-and/or artofcode LLC, copyright holder of Ghostscript, at <a
-href="mailto:raph at artofcode.com">raph at artofcode.com</a>.
+and/or Artifex Software, Inc., copyright holder of Ghostscript, at <a
+href="mailto:info at artifex.com">info at artifex.com</a>.
<h3><a name="Makefile_setup"></a>Setting up "makefile"</h3>
Modified: trunk/gs/doc/Projects.htm
===================================================================
--- trunk/gs/doc/Projects.htm 2007-06-05 23:04:12 UTC (rev 8023)
+++ trunk/gs/doc/Projects.htm 2007-06-05 23:08:49 UTC (rev 8024)
@@ -48,7 +48,7 @@
There are many projects that would improve Ghostscript and that we would
like to do, but for which we don't have enough resources. If you would like
to take responsibility for any of these projects, please <a
-href="mailto:raph at artofcode.com">contact us</a>. Additional comments on
+href="mailto:info at artifex.com">contact us</a>. Additional comments on
implementation approaches or project goals are in <I>italic type like
this</I>.
@@ -374,7 +374,7 @@
it further. We want to factor out error diffusion into a common set of
facilities that drivers can use. <I>We would like to design
these facilities so that they can easily interface to the Even-Toned
-Screening algorithms from artofcode (Raph Levien), to the extent that these
+Screening algorithms, to the extent that these
will be Open Source.</I>
<h3>Improve, or generalize, linearization for stochastic threshold
Modified: trunk/gs/doc/Readme.htm
===================================================================
--- trunk/gs/doc/Readme.htm 2007-06-05 23:04:12 UTC (rev 8023)
+++ trunk/gs/doc/Readme.htm 2007-06-05 23:08:49 UTC (rev 8024)
@@ -99,7 +99,6 @@
<a href="#Htmstyle">Htmstyle.htm</a><br>
<a href="#Issues">Issues.htm</a><br>
<a href="#Lib">Lib.htm</a><br>
-<a href="#Maintain">Maintain.htm</a><br>
<a href="#Projects">Projects.htm</a><br>
<td> <td valign=top>
<a href="#Ps-style">Ps-style.htm</a><br>
@@ -480,11 +479,6 @@
</dl>
<dl>
-<dt><a name="Maintain"></a><a href="Maintain.htm"><b>Maintain.htm</b></a>
-<dd> Assorted Ghostscript maintenance procedures. For developers.
-</dl>
-
-<dl>
<dt><a name="Make"></a><a href="Make.htm"><b>Make.htm</b></a>
<dd> How to build Ghostscript executables from the source code. See also
<a href="#Install">how to install it</a>. It's not necessary to be a highly
Modified: trunk/gs/doc/Testing.htm
===================================================================
--- trunk/gs/doc/Testing.htm 2007-06-05 23:04:12 UTC (rev 8023)
+++ trunk/gs/doc/Testing.htm 2007-06-05 23:08:49 UTC (rev 8024)
@@ -39,8 +39,7 @@
writing new testing scripts.
<p>For other information, see the <a href="Readme.htm">Ghostscript
-overview</a> and the documentation related to <a
-href="Maintain.htm">maintaining Ghostscript</a>.
+overview</a>.
<!-- [1.3 end hint] ======================================================== -->
Modified: trunk/gs/doc/Use.htm
===================================================================
--- trunk/gs/doc/Use.htm 2007-06-05 23:04:12 UTC (rev 8023)
+++ trunk/gs/doc/Use.htm 2007-06-05 23:08:49 UTC (rev 8024)
@@ -1420,7 +1420,7 @@
The Ghostscript distribution includes some Unix shell scripts to use with
Ghostscript in different environments. These are all user-contributed
code, so if you have questions, please contact the user identified in the
-file, not Aladdin Enterprises or artofcode LLC.
+file, not Artifex Software.
<dl>
<dt><b><tt>pv.sh</tt></b>
More information about the gs-cvs
mailing list