Þ•          t      Ì         Ñ       ã  Ã   ñ  O   µ  l     k  r  ¦  Þ  ì   …  ï   r  <  b	  «  Ÿ
  Ó  K       É   -  P   ÷  m   H  k  ¶  ¦  "  ì   É  ï   ¶  =  ¦               
          	                                   B<plotchangelog> is a tool to aid in visualizing a Debian changelog. The changelogs are graphed with B<gnuplot>(1)  , with the X axis of the graph denoting time of release and the Y axis denoting the debian version number of the package. Each individual release of the package is represented by a point, and the points are color coded to indicate who released that version of the package. The upstream version number of the package can also be labeled on the graph. CUSTOMIZATION Discards access to SGML catalogs; some SGML tools read all the registered catalogs at startup.  Files matching the regexp /usr/share/sgml/.*\e.cat are recognised as catalogs.  Enabled by default. Edit the generated commit message in your favorite editor before committing it. Fill out the templates for each package and display them all for verification. This is the default behavior. Finalize the changelog for a release.  Update the changelog timestamp. If the distribution is set to I<UNRELEASED>, change it to the distribution from the previous changelog entry (or another distribution as specified by B<--distribution>).  If there are no previous changelog entries and an explicit distribution has not been specified, I<unstable> will be used. This allows you to insert B<gnuplot>(1)  commands into the gnuplot script that is used to generate the graph. The commands are placed after all initialization but before the final "plot" command. This can be used to override the default look provided by this program in arbitrary ways. You can also use things like "set terminal png color" to change the output file type, which is useful in conjunction with the -s option. Unless an explicit version number is provided, the archive name is analyzed for a sequence of digits separated by dots.  If something like that is found, it is taken to be the new upstream version number.  If not, processing is aborted. Unless an explicit version number is provided, the patch file name is analyzed for a sequence of digits separated by dots.  If something like that is found, it is taken to be the new upstream version number.  If not, processing is aborted. You are using this tool at your own risk and I shall not shed a tear if your gerbil goes up in flames, your microwave attacks the stereo, or the angry slamming of your fist spills your coffee into the keyboard, which sets off a chain reaction resulting in a vast amount of money transfered from your account to mine. Project-Id-Version: devscripts
Report-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS>
POT-Creation-Date: 2010-01-06 09:13+0100
PO-Revision-Date: 2011-07-02 10:01+0000
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: English (Australia) <en_AU@li.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Launchpad-Export-Date: 2011-09-30 09:07+0000
X-Generator: Launchpad (build 14071)
 B<plotchangelog> is a tool to aid in visualising a Debian changelog. The changelogs are graphed with B<gnuplot>(1)  , with the X axis of the graph denoting time of release and the Y axis denoting the debian version number of the package. Each individual release of the package is represented by a point, and the points are colour coded to indicate who released that version of the package. The upstream version number of the package can also be labelled on the graph. CUSTOMISATION Discards access to SGML catalogues; some SGML tools read all the registered catalogues at startup.  Files matching the regexp /usr/share/sgml/.*\e.cat are recognised as catalogues.  Enabled by default. Edit the generated commit message in your favourite editor before committing it. Fill out the templates for each package and display them all for verification. This is the default behaviour. Finalise the changelog for a release.  Update the changelog timestamp. If the distribution is set to I<UNRELEASED>, change it to the distribution from the previous changelog entry (or another distribution as specified by B<--distribution>).  If there are no previous changelog entries and an explicit distribution has not been specified, I<unstable> will be used. This allows you to insert B<gnuplot>(1)  commands into the gnuplot script that is used to generate the graph. The commands are placed after all initialisation but before the final "plot" command. This can be used to override the default look provided by this program in arbitrary ways. You can also use things like "set terminal png color" to change the output file type, which is useful in conjunction with the -s option. Unless an explicit version number is provided, the archive name is analysed for a sequence of digits separated by dots.  If something like that is found, it is taken to be the new upstream version number.  If not, processing is aborted. Unless an explicit version number is provided, the patch file name is analysed for a sequence of digits separated by dots.  If something like that is found, it is taken to be the new upstream version number.  If not, processing is aborted. You are using this tool at your own risk and I shall not shed a tear if your gerbil goes up in flames, your microwave attacks the stereo, or the angry slamming of your fist spills your coffee into the keyboard, which sets off a chain reaction resulting in a vast amount of money transferred from your account to mine. 