BrowseRefs: Added 'Switch to this Ref' option

[tortoisegit/TortoiseGitJp.git] / doc / issuetrackers.txt

diff --git a/doc/issuetrackers.txt b/doc/issuetrackers.txt
index a8d83d1..7952147 100644 (file)
--- a/doc/issuetrackers.txt
+++ b/doc/issuetrackers.txt
@@ -1,10 +1,10 @@
-Integration of Subversion (GUI) clients with Bug Tracking Tools:\r
+Integration of Git (GUI) clients with Bug Tracking Tools:\r
 ================================================================================\r
 \r
 I. Preface\r
 ==========\r
 This document is primarily intended for writers of various GUI clients for \r
-Subversion.  Clients such as TortoiseSVN, Subclipse, RapidSVN, PySVN and many \r
+Git.  Clients such as TortoiseSVN, Subclipse, RapidSVN, PySVN and many \r
 others.\r
 \r
 The goal of this document is to outline a common technique for defining and then \r
@@ -14,17 +14,17 @@ II. Introduction
 ================\r
 It is very common in Software Development for changes to be related to a \r
 specific bug or issue ID. Users of bug tracking systems would like to associate \r
-the changes they make in Subversion with a specific ID in their bug tracking \r
+the changes they make in Git with a specific ID in their bug tracking \r
 system. There are already a number of people that have integrated these systems \r
-with Subversion. They typically rely on the end user entering a log message on \r
+with Git. They typically rely on the end user entering a log message on \r
 their commits in some kind of a specific format that can be parsed with a \r
 commit-hook or in some cases just on-the-fly in a web-based presentation of the \r
 commit info. This option is OK, but it is not very user-friendly and it places \r
-all of the integration within the bug tracking tool. When using a Subversion \r
+all of the integration within the bug tracking tool. When using a Git \r
 client, you can see the log message info, but there is no way to jump to the bug \r
 system.\r
 \r
-Subversion (GUI) clients can help both the users and the bug tracking tools in \r
+Git (GUI) clients can help both the users and the bug tracking tools in \r
 that task:\r
 \r
 - When the user enters a log message, a well defined line including the issue \r
@@ -40,7 +40,7 @@ the webbrowser to see the issue associated with that log message/commit.
 \r
 III. Requirements\r
 =================\r
-To make the integration with bug tracking tools possible, a Subversion client \r
+To make the integration with bug tracking tools possible, a Git client \r
 needs some information about the bug tracking tool used in a project. That \r
 information should be available inside the working copy so that clients don't \r
 have to access the repository over a possibly very slow connection to get that \r
@@ -53,7 +53,7 @@ The information a client needs is:
   bug tracking tool can recognize it. Or\r
 - a regular expression to parse the log message with to extract the issue number\r
 \r
-There are other things a Subversion (GUI) client could use to make the \r
+There are other things a Git (GUI) client could use to make the \r
 integration with bug tracking tools easier for the user, but these are \r
 essential for the integration to work.\r
 \r
@@ -82,7 +82,7 @@ showing the logmessage of a revision.
 To allow relative URLs, the following formats can be used (subset of the \r
 svn:external relative urls):\r
 ^/   relative to the repository root. Since issue trackers can not reside\r
-     below a subversion repository, the URL must contain navigations.\r
+     below a Git repository, the URL must contain navigations.\r
      For example: ^/../../issues/id?123\r
 /    relative to the server's hostname\r
 ---------\r
@@ -192,10 +192,10 @@ Please note:
 \r
 A. FAQ\r
 ======\r
-Q: Why is the integration with bug tracking tools not defined by the Subversion\r
+Q: Why is the integration with bug tracking tools not defined by the Git\r
    project?\r
-A: The Subversion developers want to keep Subversion "clean", i.e. they \r
-   concentrate on Subversions basic tasks.\r
+A: The Git developers want to keep Git "clean", i.e. they \r
+   concentrate on Gits basic tasks.\r
 \r
 Q: Why don't you use a config file located on the server or revision properties\r
    instead of folder properties?\r
@@ -206,7 +206,7 @@ A: A config file located on the server and revision properties would mean that
 \r
 Q: Isn't there a way to store the data in the repository, but having it also\r
    stored in the working copy?\r
-A: Subversion doesn't provide such a feature (yet). And there's no way to be \r
+A: Git doesn't provide such a feature (yet). And there's no way to be \r
    sure that there ever will be such a feature. So we have to make use of that\r
    what's already available.\r
    Also, if the properties are set for each folder, then you can assign a \r