1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
TITLE="The Bugzilla Guide - 3.0.4 Release"
11
HREF="index.html"><LINK
13
TITLE="Using Bugzilla"
14
HREF="using.html"><LINK
17
HREF="bugreports.html"><LINK
19
TITLE="Hints and Tips"
20
HREF="hintsandtips.html"></HEAD
31
SUMMARY="Header navigation table"
40
>The Bugzilla Guide - 3.0.4 Release</TH
48
HREF="bugreports.html"
56
>Chapter 5. Using Bugzilla</TD
62
HREF="hintsandtips.html"
80
> You should use attachments, rather than comments, for large chunks of ASCII
81
data, such as trace, debugging output files, or log files. That way, it
82
doesn't bloat the bug for everyone who wants to read it, and cause people to
83
receive fat, useless mails.
86
>You should make sure to trim screenshots. There's no need to show the
87
whole screen if you are pointing out a single-pixel problem.
90
>Bugzilla stores and uses a Content-Type for each attachment
91
(e.g. text/html). To download an attachment as a different
92
Content-Type (e.g. application/xhtml+xml), you can override this
93
using a 'content_type' parameter on the URL, e.g.
96
>&content_type=text/plain</TT
100
> If you have a really large attachment, something that does not need to
101
be recorded forever (as most attachments are), or something that is too
102
big for your database, you can mark your attachment as a
106
>, assuming the administrator of the installation
107
has enabled this feature. Big Files are stored directly on disk instead
108
of in the database. The maximum size of a <SPAN
112
normally larger than the maximum size of a regular attachment. Independently
113
of the storage system used, an administrator can delete these attachments
114
at any time. Nevertheless, if these files are stored in the database, the
117
>"allow_attachment_deletion"</SPAN
118
> parameter (which is turned off
119
by default) must be enabled in order to delete them.
122
> Also, if the administrator turned on the <SPAN
124
>"allow_attach_url"</SPAN
126
parameter, you can enter the URL pointing to the attachment instead of
127
uploading the attachment itself. For example, this is useful if you want to
128
point to an external application, a website or a very large file. Note that
129
there is no guarantee that the source file will always be available, nor
130
that its content will remain unchanged.
138
>5.7.1. Patch Viewer</A
141
>Viewing and reviewing patches in Bugzilla is often difficult due to
142
lack of context, improper format and the inherent readability issues that
143
raw patches present. Patch Viewer is an enhancement to Bugzilla designed
144
to fix that by offering increased context, linking to sections, and
145
integrating with Bonsai, LXR and CVS.</P
147
>Patch viewer allows you to:</P
155
>View patches in color, with side-by-side view rather than trying
156
to interpret the contents of the patch.</TD
160
>See the difference between two patches.</TD
164
>Get more context in a patch.</TD
168
>Collapse and expand sections of a patch for easy
173
>Link to a particular section of a patch for discussion or
178
>Go to Bonsai or LXR to see more context, blame, and
179
cross-references for the part of the patch you are looking at</TD
183
>Create a rawtext unified format diff out of any patch, no
184
matter what format it came from</TD
195
NAME="patchviewer_view"
196
>5.7.1.1. Viewing Patches in Patch Viewer</A
199
>The main way to view a patch in patch viewer is to click on the
200
"Diff" link next to a patch in the Attachments list on a bug. You may
201
also do this within the edit window by clicking the "View Attachment As
202
Diff" button in the Edit Attachment screen.</P
209
NAME="patchviewer_diff"
210
>5.7.1.2. Seeing the Difference Between Two Patches</A
213
>To see the difference between two patches, you must first view the
214
newer patch in Patch Viewer. Then select the older patch from the
215
dropdown at the top of the page ("Differences between [dropdown] and
216
this patch") and click the "Diff" button. This will show you what
217
is new or changed in the newer patch.</P
224
NAME="patchviewer_context"
225
>5.7.1.3. Getting More Context in a Patch</A
228
>To get more context in a patch, you put a number in the textbox at
229
the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
230
This will give you that many lines of context before and after each
231
change. Alternatively, you can click on the "File" link there and it
232
will show each change in the full context of the file. This feature only
233
works against files that were diffed using "cvs diff".</P
240
NAME="patchviewer_collapse"
241
>5.7.1.4. Collapsing and Expanding Sections of a Patch</A
244
>To view only a certain set of files in a patch (for example, if a
245
patch is absolutely huge and you want to only review part of it at a
246
time), you can click the "(+)" and "(-)" links next to each file (to
247
expand it or collapse it). If you want to collapse all files or expand
248
all files, you can click the "Collapse All" and "Expand All" links at the
256
NAME="patchviewer_link"
257
>5.7.1.5. Linking to a Section of a Patch</A
260
>To link to a section of a patch (for example, if you want to be
261
able to give someone a URL to show them which part you are talking
262
about) you simply click the "Link Here" link on the section header. The
263
resulting URL can be copied and used in discussion.</P
270
NAME="patchviewer_bonsai_lxr"
271
>5.7.1.6. Going to Bonsai and LXR</A
274
>To go to Bonsai to get blame for the lines you are interested in,
275
you can click the "Lines XX-YY" link on the section header you are
276
interested in. This works even if the patch is against an old
277
version of the file, since Bonsai stores all versions of the file.</P
279
>To go to LXR, you click on the filename on the file header
280
(unfortunately, since LXR only does the most recent version, line
281
numbers are likely to rot).</P
288
NAME="patchviewer_unified_diff"
289
>5.7.1.7. Creating a Unified Diff</A
292
>If the patch is not in a format that you like, you can turn it
293
into a unified diff format by clicking the "Raw Unified" link at the top
303
SUMMARY="Footer navigation table"
314
HREF="bugreports.html"
332
HREF="hintsandtips.html"
b'\\ No newline at end of file'
added
removed
docs/html/attachments.html
