From 5caa52f7461a876f7cc734148229d8af64d8dee3 Mon Sep 17 00:00:00 2001
From: Sup Yut Sum <ch3cooli@gmail.com>
Date: Wed, 14 Nov 2012 23:32:31 +0800
Subject: [PATCH] Remove commented blocks

Signed-off-by: Sup Yut Sum <ch3cooli@gmail.com>
---
 doc/source/en/TortoiseGit/tsvn_dug/dug_log.xml | 501 -------------------------
 1 file changed, 501 deletions(-)

diff --git a/doc/source/en/TortoiseGit/tsvn_dug/dug_log.xml b/doc/source/en/TortoiseGit/tsvn_dug/dug_log.xml
index 003d20eb6..4bf92122d 100644
--- a/doc/source/en/TortoiseGit/tsvn_dug/dug_log.xml
+++ b/doc/source/en/TortoiseGit/tsvn_dug/dug_log.xml
@@ -68,22 +68,6 @@
 						From the TortoiseGit context submenu
 					</para>
 				</listitem>
-				<!--
-				<listitem>
-					<para>
-						From the property page
-					</para>
-				</listitem>
-				-->
-				<!--
-				<listitem>
-					<para>
-						From the Progress dialog after an update
-						has finished. Then the Log dialog only shows those revisions
-						which were changed since your last update
-					</para>
-				</listitem>
-				-->
 			</itemizedlist>
 		</para>
 	</sect2>
@@ -140,19 +124,6 @@
 						</para>
 					</listitem>
 				</varlistentry>
-				<!--
-				<varlistentry>
-					<term>Compare and blame with working BASE</term>
-					<listitem>
-						<para>
-							Blame the selected revision, and the file in your working BASE
-							and compare the blame reports using a visual diff tool.
-							Read <xref linkend="tsvn-dug-blame-diffs"/> for more detail.
-							(files only).
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
 				<varlistentry>
 					<term>Show changes as unified diff</term>
 					<listitem>
@@ -177,49 +148,6 @@
 						</para>
 					</listitem>
 				</varlistentry>
-				<!--
-				<varlistentry>
-					<term>Compare and blame with previous revision</term>
-					<listitem>
-						<para>
-							Show the changed files dialog allowing you to select files.
-							Blame the selected revision, and the previous revision,
-							and compare the results using a visual diff tool.
-							(folders only).
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
-				<!--
-				<varlistentry>
-					<term>Save revision to...</term>
-					<listitem>
-						<para>
-							Save the selected revision to a file so you have an older
-							version of that file. (files only).
-						</para>
-					</listitem>
-				</varlistentry>
-
-				<varlistentry>
-					<term>Open / Open with...</term>
-					<listitem>
-						<para>
-							Open the selected file, either with the default viewer for
-							that file type, or with a program you choose. (files only).
-						</para>
-					</listitem>
-				</varlistentry>
-				<varlistentry>
-					<term>Blame...</term>
-					<listitem>
-						<para>
-							Blame the file up to the selected revision. (files only).
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
-				<!--
 				<varlistentry>
 					<term>Browse repository</term>
 					<listitem>
@@ -229,7 +157,6 @@
 						</para>
 					</listitem>
 				</varlistentry>
-				-->
 				<varlistentry>
 					<term>Reset (current branch) to this</term>
 					<listitem>
@@ -239,7 +166,6 @@
 						</para>
 					</listitem>
 				</varlistentry>
-
 				<varlistentry>
 					<term>Switch\Checkout to revision</term>
 					<listitem>
@@ -271,7 +197,6 @@
 						</para>
 					</listitem>
 				</varlistentry>
-
 				<varlistentry>
 					<term>Rebase (current branch) to this</term>
 					<listitem>
@@ -290,73 +215,6 @@
 						</para>
 					</listitem>
 				</varlistentry>
-				<!--
-				<varlistentry>
-					<term>Revert changes from this revision</term>
-					<listitem>
-						<para>
-							Revert changes from which were made in the selected
-							revision. The changes are reverted in your working tree so
-							this operation does <emphasis>not</emphasis> affect the
-							repository at all! Note that this will undo the changes
-							made in that revision only. It does not replace your
-							working tree with the entire file at the earlier revision.
-							This is very useful for undoing an earlier change when
-							other unrelated changes have been made since. If you have
-							made local changes, this command will merge these changes
-							into your working tree.
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
-				<!--
-				<varlistentry>
-					<term>Revert to this revision</term>
-					<listitem>
-						<para>
-							Revert to an earlier revision. If you have made several
-							changes, and then decide that you really want to go back to
-							how things were in revision N, this is the command you need.
-							Again, the changes are reverted in your working tree so
-							this operation does <emphasis>not</emphasis> affect the
-							repository until you commit the changes. Note that this
-							will undo <emphasis>all</emphasis> changes made after the
-							selected revision, replacing the file/folder with the
-							earlier version. If you have made local changes, this
-							command will merge these changes into your working tree.
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
-				<!--
-				<varlistentry>
-					<term>Merge revision to...</term>
-					<listitem>
-						<para>
-							Merge the selected revision(s) into a different working tree.
-							A folder selection dialog allows you to choose the working
-							copy to merge into, but after that there is no confirmation
-							dialog, nor any opportunity to try a test merge. It is a good
-							idea to merge into an unmodified working tree so that you can
-							revert the changes if it doesn't work out!
-							This is a useful feature if you want to merge selected
-							revisions from one branch to another.
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
-				<!--
-				<varlistentry>
-					<term>Checkout...</term>
-					<listitem>
-						<para>
-							Make a fresh checkout of the selected folder at the selected
-							revision. This brings up a dialog for you to confirm the
-							URL and revision, and select a location for the checkout.
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
 				<varlistentry>
 					<term>Export this version...</term>
 					<listitem>
@@ -367,29 +225,6 @@
 						</para>
 					</listitem>
 				</varlistentry>
-				<!--
-				<varlistentry>
-					<term>Edit author / log message</term>
-					<listitem>
-						<para>
-							Edit the log message or author attached to a previous commit.
-							Read <xref linkend="tsvn-dug-showlog-4"/> to find out
-							how this works.
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
-				<!--
-				<varlistentry>
-					<term>Show revision properties</term>
-					<listitem>
-						<para>
-							View and edit any revision property, not just log message
-							and author. Refer to <xref linkend="tsvn-dug-showlog-4"/>.
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
 				<varlistentry>
 					<term>Copy to clipboard</term>
 					<listitem>
@@ -447,28 +282,8 @@
 							difference tool. The default Diff-Tool is TortoiseMerge
 							which is supplied with TortoiseGit.
 						</para>
-						<!--
-						<para>
-							If you select this option for a folder, a further dialog pops
-							up listing the changed files and offering you further
-							diff options. Read more about the Compare Revisions
-							dialog in <xref linkend="tsvn-dug-compare-revs"/>.
-						</para>
-						-->
 					</listitem>
 				</varlistentry>
-				<!--
-				<varlistentry>
-					<term>Blame revisions</term>
-					<listitem>
-						<para>
-							Blame the two revisions and compare the blame reports using
-							a visual difference tool.
-							Read <xref linkend="tsvn-dug-blame-diffs"/> for more detail.
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
 				<varlistentry>
 					<term>Show differences as unified diff</term>
 					<listitem>
@@ -527,16 +342,6 @@
 			You can combine select commits to one commit. And cherry pick
 			these commits to current branch.
 		</para>
-		<!--
-		<para>
-			You can also choose to merge the selected revisions to another
-			working tree, as described above.
-		</para>
-		<para>
-			If all selected revisions have the same author, you can edit
-			the author of all those revisions in one go.
-		</para>
-		-->
 		<para>
 			<figure id="tsvn-dug-showlog-2-dia-2">
 				<title>The Log Dialog Bottom Pane with Context Menu</title>
@@ -544,30 +349,6 @@
 			</figure>
 			The bottom pane of the Log dialog also has a context menu that allows you to
 			<variablelist>
-				<!--
-				<varlistentry>
-					<term>Show changes</term>
-					<listitem>
-						<para>
-							Show changes made in the selected revision for the
-							selected file. This context menu is only available for
-							files shown as <emphasis>modified</emphasis>.
-						</para>
-					</listitem>
-				</varlistentry>
-				<varlistentry>
-					<term>Blame changes</term>
-					<listitem>
-						<para>
-							Blame the selected revision and the previous revision for the
-							selected file, and compare the blame reports
-							using a visual diff tool.
-							Read <xref linkend="tsvn-dug-blame-diffs"/> for more detail.
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
-
 				<varlistentry>
 					<term>Show as unified diff</term>
 					<listitem>
@@ -687,31 +468,6 @@
 						</para>
 					</listitem>
 				</varlistentry>
-
-				<!--
-				<varlistentry>
-					<term>Show properties</term>
-					<listitem>
-						<para>
-							View the Git properties for the selected item.
-						</para>
-					</listitem>
-				</varlistentry>
-				-->
-				<!--
-
-				<varlistentry>
-					<term>Get merge logs</term>
-					<listitem>
-						<para>
-							Show the revision log for the selected single file,
-							including merged changes. Find out more in
-							<xref linkend="tsvn-dug-showlog-mergetrack"/>.
-						</para>
-					</listitem>
-				</varlistentry>
-
-				-->
 			</variablelist>
 		</para>
 		<tip>
@@ -719,223 +475,8 @@
 				You may notice that sometimes we refer to changes and other times
 				to differences. What's the difference?
 			</para>
-			<!--
-			<para>
-				Git uses commit hash to mean 2 different things.
-				A revision generally represents the state of the repository at
-				a point in time, but it can also be used to represent the changeset
-				which created that revision, eg. <quote>Done in r1234</quote> means
-				that the changes committed in r1234 implement feature X.
-				To make it clearer which sense is being used, we use two
-				different terms.
-			</para>
-			<para>
-				If you select two revisions N and M, the context menu will offer
-				to show the <emphasis>difference</emphasis> between those two
-				revisions. In Git terms this is
-				<literal>diff -r M:N</literal>.
-			</para>
-			<para>
-				If you select a single revision N, the context menu will offer
-				to show the <emphasis>changes</emphasis> made in that revision.
-				In Git terms this is <literal>diff -r N-1:N</literal>
-				or <literal>diff -c N</literal>.
-			</para>
-			<para>
-				The bottom pane shows the files changed in all selected revisions,
-				so the context menu always offers to show <emphasis>changes</emphasis>.
-			</para>
-			-->
 		</tip>
 	</sect2>
-	<!--
-	<sect2 id="tsvn-dug-showlog-3">
-		<title>Getting more log messages</title>
-		<para>
-			The Log dialog does not always show all changes ever made for a
-			number of reasons:
-			<itemizedlist>
-				<listitem>
-					<para>
-						For a large repository there may be hundreds or even
-						thousands of changes and fetching them all could take
-						a long time. Normally you are only interested in the
-						more recent changes. By default, the number of log
-						messages fetched is limited to 100, but you can change
-						this value in
-						<menuchoice>
-							<guimenu>TortoiseGit</guimenu>
-							<guimenuitem>Settings</guimenuitem>
-						</menuchoice>
-						(<xref linkend="tsvn-dug-settings-dialogs"/>),
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						When the <guilabel>Stop on copy/rename</guilabel>
-						box is checked, Show Log will stop at the point that
-						the selected file or folder was copied from somewhere
-						else within the repository. This can be useful when
-						looking at branches (or tags) as it stops at the root
-						of that branch, and gives a quick indication of changes
-						made in that branch only.
-					</para>
-					<para>
-						Normally you will want to leave this option unchecked.
-						TortoiseGit remembers the state of the checkbox, so
-						it will respect your preference.
-					</para>
-					<para>
-						When the Show Log dialog is invoked from within the
-						Merge dialog, the box is always checked by default.
-						This is because merging is most often looking at
-						changes on branches, and going back beyond the root
-						of the branch does not make sense in that instance.
-					</para>
-					<para>
-						Note that Git currently implements renaming
-						as a copy/delete pair, so renaming a file or folder
-						will also cause the log display to stop if this
-						option is checked.
-					</para>
-				</listitem>
-			</itemizedlist>
-		</para>
-		<para>
-			If you want to see more log messages, click the
-			<guibutton>Next 100</guibutton> to retrieve the next 100 log messages.
-			You can repeat this as many times as needed.
-		</para>
-		<para>
-			Next to this button there is a multi-function button which remembers
-			the last option you used it for. Click on the arrow to see the other
-			options offered.
-		</para>
-		<para>
-			Use <guibutton>Show Range ...</guibutton> if you want to view a specific
-			range of revisions. A dialog will then prompt you to enter the start
-			and end revision.
-		</para>
-		<para>
-			Use <guibutton>Show All</guibutton> if you want to see
-			<emphasis>all</emphasis> log messages from HEAD right back to revision 1.
-		</para>
-	</sect2>
-	-->
-	<!--
-	<sect2 id="tsvn-dug-showlog-current-rev">
-		<title>Current Working Tree Revision</title>
-		<para>
-			Because the log dialog shows you the log from HEAD, not from the
-			current working tree revision, it often happens that there are
-			log messages shown for content which has not yet been updated
-			in your working tree. To help make this clearer, the commit
-			message which corresponds to the revision you have in your
-			working tree is shown in bold.
-		</para>
-		<para>
-			By default this only works for files. This is because the
-			update revision for a folder may not correspond to the update
-			revision of its content, and the only way to find the effective
-			update revision for the folder is to crawl the working tree.
-			This can be a slow operation for large working trees so if
-			you want to enable this feature you must create a
-			<literal>DWORD</literal> registry key with value 1 at
-			<literal>HKCU\Software\TortoiseGit\RecursiveLogRev</literal>.
-		</para>
-	</sect2>
-	-->
-	<!--
-	<sect2 id="tsvn-dug-showlog-mergetrack">
-		<title>Merge Tracking Features</title>
-		<indexterm>
-			<primary>merge tracking log</primary>
-		</indexterm>
-		<para>
-			Git 1.5 and later keeps a record of merges using properties.
-			This allows us to get a more detailed history of merged changes.
-			For example, if you develop a new feature on a branch and then merge
-			that branch back to trunk, the feature development will show up on
-			the trunk log as a single commit for the merge, even though there
-			may have been 1000 commits during branch development.
-		</para>
-		<figure id="tsvn-dug-showlog-dia-mergetrack">
-			<title>The Log Dialog Showing Merge Tracking Revisions</title>
-			<graphic fileref="../images/LogMergeTrack.png"/>
-		</figure>
-		<para>
-			If you want to see the detail of which revisions were merged as part
-			of that commit, use the <guilabel>Include merged revisions</guilabel>
-			checkbox. This will fetch the log messages again, but will also
-			interleave the log messages from revisions which were merged.
-			Merged revisions are shown in grey because they represent changes
-			made on a different part of the tree.
-		</para>
-		<para>
-			Of course, merging is never simple! During feature development on the
-			branch there will probably be occasional merges back from trunk to
-			keep the branch in sync with the main line code. So the merge history
-			of the branch will also include another layer of merge history.
-			These different layers are shown in the log dialog using indentation
-			levels.
-		</para>
-	</sect2>
-	-->
-	<!--
-	<sect2 id="tsvn-dug-showlog-4">
-		<title>Changing the Log Message and Author</title>
-		<indexterm>
-			<primary>edit log/author</primary>
-		</indexterm>
-		<indexterm>
-			<primary>revision properties</primary>
-		</indexterm>
-		<indexterm>
-			<primary>revprops</primary>
-		</indexterm>
-		<para>
-			Revision properties are completely different from the Git
-			properties of each item. Revprops are descriptive items which are
-			associated with one specific revision number in the repository,
-			such as log message, commit date and committer name (author).
-		</para>
-		<para>
-			Sometimes you might want to change a log message you once entered,
-			maybe because there's a spelling error in it or you want to
-			improve the message or change it for other reasons. Or you want to
-			change the author of the commit because you forgot to set up
-			authentication or...
-		</para>
-		<para>
-			Git lets you change revision properties any time you want.
-			But since such changes can't be
-			undone (those changes are not versioned) this feature is disabled
-			by default. To make this work, you must set up a pre-revprop-change
-			hook. Please refer to the chapter on
-			<ulink url="http://svnbook.red-bean.com/en/1.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks">
-				<citetitle>Hook Scripts</citetitle>
-			</ulink>
-			in the Git Book for details about how to do that.
-			Read <xref linkend="tsvn-repository-hooks"/> to find some further
-			notes on implementing hooks on a Windows machine.
-		</para>
-		<para>
-			Once you've set up your server with the required hooks, you can
-			change the author and log message (or any other revprop) of any revision,
-			using the context menu from the top pane of the Log dialog.
-			You can also edit a log message using the context menu for the middle pane.
-		</para>
-		<warning>
-			<para>
-				Because Git's revision properties are not versioned, making
-				modifications to such a property (for example, the
-				<literal>svn:log</literal> commit
-				message property) will overwrite the previous value of that
-				property <emphasis>forever</emphasis>.
-			</para>
-		</warning>
-	</sect2>
-	-->
 	<sect2 id="tsvn-dug-showlog-filter">
 		<title>Filtering Log Messages</title>
 		<indexterm>
@@ -996,26 +537,6 @@
 			<guilabel>First Parent</guilabel> just follow up first parent commit. This will
 			help understand overwhole history.
 		</para>
-		<!--
-		<para>
-			Sometimes your working practices will require log messages to follow
-			a particular format, which means that the text describing the changes
-			is not visible in the abbreviated summary shown in the top pane.
-			The property <literal>tsvn:logsummary</literal> can be used to
-			extract a portion of the log message to be shown in the top pane.
-			Read <xref linkend="tsvn-dug-propertypage-tsvn-props"/> to find
-			out how to use this property.
-		</para>
-		<tip>
-			<title>No Log Formatting from Repository Browser</title>
-			<para>
-				Because the formatting depends upon accessing Git
-				properties, you will only see the results when using a checked
-				out working tree. Fetching properties remotely is a slow operation,
-				so you will not see this feature in action from the repo browser.
-			</para>
-		</tip>
-		-->
 	</sect2>
 	<sect2 id="tsvn-dug-showlog-5">
 		<?dbhh topicname="HIDD_STATGRAPH"?>
@@ -1100,18 +621,6 @@
 			then the statistics will not tell you very much.
 		</para>
 	</sect2>
-	<!--
-	<sect2 id="tsvn-dug-showlog-cache">
-		<?dbhh topicname="HIDD_GOOFFLINE"?>
-		<title>Offline Mode</title>
-		<para>
-			If the server is not reachable, and you have log caching enabled
-			you can use the log dialog and revision graph in offline mode.
-			This uses data from the cache, which allows you to continue working
-			although the information may not be up-to-date or even complete.
-		</para>
-	</sect2>
-	-->
 	<sect2 id="tsvn-dug-showlog-refresh">
 		<title>Refreshing the View</title>
 		<para>
@@ -1120,15 +629,5 @@
 			are using the log cache (enabled by default), this will check the
 			repository for newer messages and fetch only the new ones.
 		</para>
-		<!--
-		<para>
-			If you are using the log cache and you think the message content
-			or author may have changed, you can use <keycap>Shift-F5</keycap>
-			or <keycap>Ctrl-F5</keycap> to re-fetch the displayed messages from
-			the server and update the log cache. Note that this only affects
-			messages currently shown and does not invalidate the entire cache
-			for that repository.
-		</para>
-		-->
 	</sect2>
 </sect1>
-- 
2.11.4.GIT