File: s_40.html

package info (click to toggle)
povray 1%3A3.6.1-12
  • links: PTS
  • area: non-free
  • in suites: lenny, squeeze
  • size: 31,084 kB
  • ctags: 20,310
  • sloc: ansic: 110,032; cpp: 86,573; sh: 13,595; pascal: 5,942; asm: 2,994; makefile: 1,753; ada: 1,637
file content (150 lines) | stat: -rw-r--r-- 4,790 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150

<!--  This file copyright Persistence of Vision Raytracer Pty. Ltd. 2003-2004  -->
<html> 
<head>
  
<!--  NOTE: In order to users to help find information about POV-Ray using  -->
 
<!--  web search engines, we ask you to *not* let them index documentation  -->
 
<!--  mirrors because effectively, when searching, users will get hundreds  -->
 
<!--  of results containing the same information! For this reason, the two  -->
 
<!--  meta tags below disable archiving and indexing of this page by all  -->
 
<!--  search engines that support these meta tags.  -->
 
 <meta content="noarchive" name="robots">
   
 <meta content="noindex" name="robots">
   
 <meta content="no-cache" http-equiv="Pragma">
   
 <meta content="0" http-equiv="expires">
   
<title>1.7.5 Bug Reporting via our News Server</title>
 <link href="povray35.css" rel="stylesheet" type="text/css"> 
</head>
 <body> 
<table class="NavBar" width="100%">
  
 <tr>
   
  <td align="left" nowrap="" valign="middle" width="32">
    <a href="s_39.html"><img alt="previous" border="0" src="prev.png"></a> 
   
  </td>
   
  <td align="left" valign="middle" width="30%">
    <a href="s_39.html">1.7.4 Bug Reporting via Email</a> 
  </td>
   
  <td align="center" valign="middle">
    <strong class="NavBar">POV-Ray 3.6 for UNIX documentation</strong><br> <strong>1.7.5 
   Bug Reporting via our News Server</strong> 
  </td>
   
  <td align="right" valign="middle" width="30%">
    <a href="s_41.html">1.8 Speed Considerations</a> 
  </td>
   
  <td align="right" nowrap="" valign="middle" width="32">
    <a href="s_41.html"><img alt="next" border="0" src="next.png"></a> 
   
  </td>
   
 </tr>
  
</table>
 
<h3><a name="s01_07_05">1.7.5 </a>Bug Reporting via our News Server</h3>

<p>
  Bug reports may be lodged about POV-Ray by posting them in the appropriate group on <a href="http://news.povray.org/" target="new">our 
 news server</a>. See <a href="http://www.povray.org/groups.html" target="new">our list of groups</a> for information 
 about the server, and particularly for information as to which group to use. The newsgroups are monitored by a 
 dedicated group of folks known as the POV-Ray <a href="http://tag.povray.org" target="new">Technical Assistance Group</a>, 
 or 'TAG' for short. The TAG will take note of any properly-lodged bug reports and pass them on to the developers. 
 They, and other users, will often lend new users a hand in getting up to speed. 
</p>

<p>
  You may like to remember, however, that no matter where you end up getting assistance from, users who show that 
 they have looked in the docs and read the VFAQ etc will be much more likely to receive the response they want than 
 someone who obviously has not done so. 
</p>

<p>
  Any messages or reports sent to us may (not necessarily will, but may) be reposted by us in our newsgroups, on 
 USENET, or on our web site. If you do not wish your communication to be posted in this manner, please do not send us 
 any. 
</p>

<p>
  You should not expect any reply to bug reports. 
</p>

<p>
  The minimum information to include in your bug report is 
</p>

<ol>
 
 <li>
   The version number of POV-Ray for Unix. 
 </li>

 <li>
   Your operating system or GNU/Linux distribution and version. It's surprising how many people fail to provide this 
  basic piece of information. We need to know what version of Unix you are running. 
 </li>

 <li>
   Your computer; what processor and how much memory. 
 </li>

 <li>
   A complete description of the problem and what led up to it. It will make it a lot easier to track down if you 
  can include a scene file that will cause the problem. If the file is large, try removing parts until you have the 
  minimum scene file that will cause the problem. 
 </li>

</ol>

<p class="Warning">
  <strong>Note:</strong> If posting on the news group or emailing someone for support, <em>never, ever</em> 
 include file attachments without asking first. The only exception is posting to a specifically- designated binaries 
 group on the POV-Ray news server. 
</p>
 <br> 
<table class="NavBar" width="100%">
  
 <tr>
   
  <td align="left" nowrap="" valign="middle" width="32">
    <a href="s_39.html"><img alt="previous" border="0" src="prev.png"></a> 
   
  </td>
   
  <td align="left" valign="middle" width="30%">
    <a href="s_39.html">1.7.4 Bug Reporting via Email</a> 
  </td>
   
  <td align="center" valign="middle">
    <strong>1.7.5 Bug Reporting via our News Server</strong> 
  </td>
   
  <td align="right" valign="middle" width="30%">
    <a href="s_41.html">1.8 Speed Considerations</a> 
  </td>
   
  <td align="right" nowrap="" valign="middle" width="32">
    <a href="s_41.html"><img alt="next" border="0" src="next.png"></a> 
   
  </td>
   
 </tr>
  
</table>
 </body> </html>