aboutsummaryrefslogtreecommitdiffstats
path: root/docs/html/scm.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/html/scm.html')
-rw-r--r--docs/html/scm.html169
1 files changed, 0 insertions, 169 deletions
diff --git a/docs/html/scm.html b/docs/html/scm.html
deleted file mode 100644
index 87dd195f1..000000000
--- a/docs/html/scm.html
+++ /dev/null
@@ -1,169 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Perforce SCM</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"><LINK
-REL="PREVIOUS"
-TITLE="CVS"
-HREF="cvs.html"><LINK
-REL="NEXT"
-TITLE="Tinderbox"
-HREF="tinderbox.html"></HEAD
-><BODY
-CLASS="SECTION"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="cvs.html"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Integrating Bugzilla with Third-Party Tools</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="tinderbox.html"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECTION"
-><H1
-CLASS="SECTION"
-><A
-NAME="SCM"
->5.3. Perforce SCM</A
-></H1
-><P
-> Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
- You can find the main project page at
- <A
-HREF="http://www.ravenbrook.com/project/p4dti/"
-TARGET="_top"
-> http://www.ravenbrook.com/project/p4dti</A
->. "p4dti" is now an officially
- supported product from Perforce, and you can find the "Perforce Public Depot"
- p4dti page at <A
-HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
-TARGET="_top"
-> http://public.perforce.com/public/perforce/p4dti/index.html</A
->.
- </P
-><P
-> Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
- p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
- patches for 2.12 will be out shortly. Check the project page regularly for updates, or
- take the given patches and patch it manually. p4dti is designed to support multiple defect
- trackers, and maintains its own documentation for it. Please consult the pages linked
- above for further information.
- </P
-><P
-> Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
- to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
- have synchronization problems, the easiest way to avoid them is to only put the bug
- information, comments, etc. into Bugzilla, and not into the Perforce change records.
- They will link anyway; merely reference the bug ID fixed in your change description,
- and put a comment into Bugzilla
- giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
- question.
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="cvs.html"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="tinderbox.html"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->CVS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="integration.html"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Tinderbox</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file