1 <?xml version="1.0" encoding="UTF-8"?>
\r
2 <!DOCTYPE sect1 SYSTEM "../../../dtd/dblite.dtd">
\r
3 <sect1 id="tsvn-dug-showlog">
\r
4 <title>Revision Log Dialog</title>
\r
6 <primary>log</primary>
\r
9 <primary>history</primary>
\r
12 <primary>commit messages</primary>
\r
15 <primary>log messages</primary>
\r
17 <?dbhh topicname="HIDD_LOGMESSAGE"?>
\r
19 For every change you make and commit, you should provide
\r
20 a log message for that change. That way you can later find out
\r
21 what changes you made and why, and you have a detailed log for
\r
22 your development process.
\r
25 The Revision Log Dialog retrieves all those log messages and shows them
\r
27 The display is divided into 3 panes.
\r
31 The top pane shows a list of revisions where changes to the
\r
32 file/folder have been committed. This summary includes the
\r
33 date and time, the person who committed the revision and the
\r
34 start of the log message.
\r
37 Lines shown in bold indicate that that is HEAD commit.
\r
42 The middle pane shows the full log message for the selected
\r
48 The bottom pane shows a list of all files and folders that
\r
49 were changed as part of the selected revision.
\r
53 But it does much more than that - it provides context menu
\r
54 commands which you can use to get even more information about the
\r
57 <sect2 id="tsvn-dug-showlog-1">
\r
58 <title>Invoking the Revision Log Dialog</title>
\r
60 <figure id="tsvn-dug-showlog-1-dia-1">
\r
61 <title>The Revision Log Dialog</title>
\r
62 <graphic fileref="../images/LogMessages.png"/>
\r
64 There are several places from where you can show the Log dialog:
\r
68 From the TortoiseGit context submenu
\r
74 From the property page
\r
81 From the Progress dialog after an update
\r
82 has finished. Then the Log dialog only shows those revisions
\r
83 which were changed since your last update
\r
90 <sect2 id="tsvn-dug-showlog-actions">
\r
91 <title>Revision Log Actions</title>
\r
93 The top pane has an <guilabel>Actions</guilabel> column containing
\r
94 icons that summarize what has been done in that revision.
\r
95 There are four different icons, each shown in its own column.
\r
98 <graphic fileref="../images/ActionModifiedIcon.png"/>
\r
99 If a revision modified a file or directory, the
\r
100 <emphasis>modified</emphasis> icon is shown in the first column.
\r
103 <graphic fileref="../images/ActionAddedIcon.png"/>
\r
104 If a revision added a file or directory, the
\r
105 <emphasis>added</emphasis> icon is shown in the second column.
\r
108 <graphic fileref="../images/ActionDeletedIcon.png"/>
\r
109 If a revision deleted a file or directory, the
\r
110 <emphasis>deleted</emphasis> icon is shown in the third column.
\r
113 <graphic fileref="../images/ActionReplacedIcon.png"/>
\r
114 If a revision replaced(rename) a file, the
\r
115 <emphasis>replaced</emphasis> icon is shown in the fourth column.
\r
118 <sect2 id="tsvn-dug-showlog-2">
\r
119 <title>Getting Additional Information</title>
\r
121 <figure id="tsvn-dug-showlog-2-dia-1">
\r
122 <title>The Revision Log Dialog Top Pane with Context Menu</title>
\r
123 <graphic fileref="../images/LogContextMenu.png"/>
\r
125 The top pane of the Log dialog has a context menu that allows you to
\r
126 access much more information. Some of these menu entries appear only
\r
127 when the log is shown for a file, and some only when the log is shown
\r
131 <term>Compare with working copy</term>
\r
134 Compare the selected revision with your working copy.
\r
135 The default Diff-Tool is TortoiseMerge which
\r
136 is supplied with TortoiseGit.
\r
137 If the log dialog is for a folder, this will show you a list
\r
138 of changed files, and allow you to review the changes made
\r
139 to each file individually.
\r
145 <term>Compare and blame with working BASE</term>
\r
148 Blame the selected revision, and the file in your working BASE
\r
149 and compare the blame reports using a visual diff tool.
\r
150 Read <xref linkend="tsvn-dug-blame-diffs"/> for more detail.
\r
157 <term>Show changes as unified diff</term>
\r
160 View the changes made in the selected revision as a
\r
161 Unified-Diff file (GNU patch format). This shows
\r
162 only the differences with a few lines of context. It
\r
163 is harder to read than a visual file compare, but will
\r
164 show all file changes together in a compact format.
\r
169 <term>Compare with previous revision</term>
\r
172 Compare the selected revision with the previous revision.
\r
173 This works in a similar manner to comparing with your
\r
175 For folders this option will first show the changed files
\r
176 dialog allowing you to select files to compare.
\r
182 <term>Compare and blame with previous revision</term>
\r
185 Show the changed files dialog allowing you to select files.
\r
186 Blame the selected revision, and the previous revision,
\r
187 and compare the results using a visual diff tool.
\r
195 <term>Save revision to...</term>
\r
198 Save the selected revision to a file so you have an older
\r
199 version of that file. (files only).
\r
205 <term>Open / Open with...</term>
\r
208 Open the selected file, either with the default viewer for
\r
209 that file type, or with a program you choose. (files only).
\r
214 <term>Blame...</term>
\r
217 Blame the file up to the selected revision. (files only).
\r
224 <term>Browse repository</term>
\r
227 Open the repository browser to examine the selected file or
\r
228 folder in the repository as it was at the selected revision.
\r
234 <term>Reset (current branch) to this</term>
\r
237 Reset current branch HEAD to selected commit.
\r
238 <!-- todo refer reset -->
\r
244 <term>Switch\Checkout to revision</term>
\r
247 Update your working copy to the selected revision.
\r
248 Useful if you want to have your working copy reflect
\r
249 a time in the past, or if there have been further commits to
\r
250 the repository and you want to update your working copy one
\r
257 <term>Create branch from revision</term>
\r
260 Create a branch from a selected revision.
\r
261 This is useful e.g.
\r
266 <term>Create tag from revision</term>
\r
269 Create a tag from a selected revision.
\r
270 This is useful e.g.
\r
277 <term>Rebase (current branch) to this</term>
\r
280 Rebase current branch to selected commit.
\r
281 <!-- todo refer rebase -->
\r
286 <term>Cherry Pick this commit</term>
\r
289 Cherry Pick this commit to current branch
\r
290 <!-- todo refer cherry pick -->
\r
296 <term>Revert changes from this revision</term>
\r
299 Revert changes from which were made in the selected
\r
300 revision. The changes are reverted in your working copy so
\r
301 this operation does <emphasis>not</emphasis> affect the
\r
302 repository at all! Note that this will undo the changes
\r
303 made in that revision only. It does not replace your
\r
304 working copy with the entire file at the earlier revision.
\r
305 This is very useful for undoing an earlier change when
\r
306 other unrelated changes have been made since. If you have
\r
307 made local changes, this command will merge these changes
\r
308 into your working copy.
\r
315 <term>Revert to this revision</term>
\r
318 Revert to an earlier revision. If you have made several
\r
319 changes, and then decide that you really want to go back to
\r
320 how things were in revision N, this is the command you need.
\r
321 Again, the changes are reverted in your working copy so
\r
322 this operation does <emphasis>not</emphasis> affect the
\r
323 repository until you commit the changes. Note that this
\r
324 will undo <emphasis>all</emphasis> changes made after the
\r
325 selected revision, replacing the file/folder with the
\r
326 earlier version. If you have made local changes, this
\r
327 command will merge these changes into your working copy.
\r
334 <term>Merge revision to...</term>
\r
337 Merge the selected revision(s) into a different working copy.
\r
338 A folder selection dialog allows you to choose the working
\r
339 copy to merge into, but after that there is no confirmation
\r
340 dialog, nor any opportunity to try a test merge. It is a good
\r
341 idea to merge into an unmodified working copy so that you can
\r
342 revert the changes if it doesn't work out!
\r
343 This is a useful feature if you want to merge selected
\r
344 revisions from one branch to another.
\r
351 <term>Checkout...</term>
\r
354 Make a fresh checkout of the selected folder at the selected
\r
355 revision. This brings up a dialog for you to confirm the
\r
356 URL and revision, and select a location for the checkout.
\r
362 <term>Export this version...</term>
\r
365 Export the selected file/folder at the selected
\r
366 revision. This brings up a dialog for you to confirm the
\r
367 URL and revision, and select a location for the export.
\r
373 <term>Edit author / log message</term>
\r
376 Edit the log message or author attached to a previous commit.
\r
377 Read <xref linkend="tsvn-dug-showlog-4"/> to find out
\r
385 <term>Show revision properties</term>
\r
388 View and edit any revision property, not just log message
\r
389 and author. Refer to <xref linkend="tsvn-dug-showlog-4"/>.
\r
395 <term>Copy to clipboard</term>
\r
398 Copy the log details of the selected revisions to the clipboard.
\r
399 This will copy the revision number, author, date, log message
\r
400 and the list of changed items for each revision.
\r
405 <term>Search log messages...</term>
\r
408 Search log messages for the text you enter. This searches
\r
409 the log messages that you entered and also the action summaries
\r
410 created by Git (shown in the bottom pane). The search
\r
411 is not case sensitive.
\r
416 <term>Format Patch...</term>
\r
419 Create Patchs from this commit.
\r
426 <figure id="tsvn-dug-showlog-2-dia-1a">
\r
427 <title>Top Pane Context Menu for 2 Selected Revisions</title>
\r
428 <graphic fileref="../images/LogContextMenu1.png"/>
\r
430 If you select two revisions at once (using the usual
\r
431 <keycap>Ctrl</keycap>-modifier), the context menu changes and
\r
432 gives you fewer options:
\r
435 <term>Compare revisions</term>
\r
438 Compare the two selected revisions using a visual
\r
439 difference tool. The default Diff-Tool is TortoiseMerge
\r
440 which is supplied with TortoiseGit.
\r
444 If you select this option for a folder, a further dialog pops
\r
445 up listing the changed files and offering you further
\r
446 diff options. Read more about the Compare Revisions
\r
447 dialog in <xref linkend="tsvn-dug-compare-revs"/>.
\r
454 <term>Blame revisions</term>
\r
457 Blame the two revisions and compare the blame reports using
\r
458 a visual difference tool.
\r
459 Read <xref linkend="tsvn-dug-blame-diffs"/> for more detail.
\r
465 <term>Show differences as unified diff</term>
\r
468 View the differences between the two selected revisions
\r
469 as a Unified-Diff file. This works for files and folders.
\r
474 <term>Combine to one commit</term>
\r
477 Combine continuous commits to one commit.
\r
482 <term>Cherry Pick this version</term>
\r
485 Cherry Pick Chosen Commits.
\r
490 <term>Fomat Patch...</term>
\r
493 Create patchs between chosen two commits.
\r
498 <term>Copy to clipboard</term>
\r
501 Copy log messages to clipboard as described above.
\r
506 <term>Search log messages...</term>
\r
509 Search log messages as described above.
\r
517 If you select two or more revisions (using the usual
\r
518 <keycap>Ctrl</keycap> or <keycap>Shift</keycap> modifiers),
\r
519 You can combine select commits to one commit. And cherry pick
\r
520 these commits to current branch.
\r
524 You can also choose to merge the selected revisions to another
\r
525 working copy, as described above.
\r
528 If all selected revisions have the same author, you can edit
\r
529 the author of all those revisions in one go.
\r
533 <figure id="tsvn-dug-showlog-2-dia-2">
\r
534 <title>The Log Dialog Bottom Pane with Context Menu</title>
\r
535 <graphic fileref="../images/LogContextMenu2.png"/>
\r
537 The bottom pane of the Log dialog also has a context menu that allows you to
\r
541 <term>Show changes</term>
\r
544 Show changes made in the selected revision for the
\r
545 selected file. This context menu is only available for
\r
546 files shown as <emphasis>modified</emphasis>.
\r
551 <term>Blame changes</term>
\r
554 Blame the selected revision and the previous revision for the
\r
555 selected file, and compare the blame reports
\r
556 using a visual diff tool.
\r
557 Read <xref linkend="tsvn-dug-blame-diffs"/> for more detail.
\r
562 <term>Show as unified diff</term>
\r
565 Show file changes in unified diff format.
\r
566 This context menu is only available for
\r
567 files shown as <emphasis>modified</emphasis>.
\r
573 <term>Open / Open with...</term>
\r
576 Open the selected file, either with the default viewer for
\r
577 that file type, or with a program you choose.
\r
582 <term>Blame...</term>
\r
585 Opens the Blame dialog, allowing you to blame up to the
\r
592 <term>Revert changes from this revision</term>
\r
595 Revert the changes made to the selected file in that revision.
\r
600 <term>Show properties</term>
\r
603 View the Git properties for the selected item.
\r
610 <term>Show log</term>
\r
613 Show the revision log for the selected single file.
\r
618 <term>Get merge logs</term>
\r
621 Show the revision log for the selected single file,
\r
622 including merged changes. Find out more in
\r
623 <xref linkend="tsvn-dug-showlog-mergetrack"/>.
\r
628 <term>Save revision to...</term>
\r
631 Save the selected revision to a file so you
\r
632 have an older version of that file.
\r
641 You may notice that sometimes we refer to changes and other times
\r
642 to differences. What's the difference?
\r
646 Git uses commit hash to mean 2 different things.
\r
647 A revision generally represents the state of the repository at
\r
648 a point in time, but it can also be used to represent the changeset
\r
649 which created that revision, eg. <quote>Done in r1234</quote> means
\r
650 that the changes committed in r1234 implement feature X.
\r
651 To make it clearer which sense is being used, we use two
\r
655 If you select two revisions N and M, the context menu will offer
\r
656 to show the <emphasis>difference</emphasis> between those two
\r
657 revisions. In Git terms this is
\r
658 <literal>diff -r M:N</literal>.
\r
661 If you select a single revision N, the context menu will offer
\r
662 to show the <emphasis>changes</emphasis> made in that revision.
\r
663 In Git terms this is <literal>diff -r N-1:N</literal>
\r
664 or <literal>diff -c N</literal>.
\r
667 The bottom pane shows the files changed in all selected revisions,
\r
668 so the context menu always offers to show <emphasis>changes</emphasis>.
\r
674 <sect2 id="tsvn-dug-showlog-3">
\r
675 <title>Getting more log messages</title>
\r
677 The Log dialog does not always show all changes ever made for a
\r
682 For a large repository there may be hundreds or even
\r
683 thousands of changes and fetching them all could take
\r
684 a long time. Normally you are only interested in the
\r
685 more recent changes. By default, the number of log
\r
686 messages fetched is limited to 100, but you can change
\r
689 <guimenu>TortoiseGit</guimenu>
\r
690 <guimenuitem>Settings</guimenuitem>
\r
692 (<xref linkend="tsvn-dug-settings-dialogs"/>),
\r
697 When the <guilabel>Stop on copy/rename</guilabel>
\r
698 box is checked, Show Log will stop at the point that
\r
699 the selected file or folder was copied from somewhere
\r
700 else within the repository. This can be useful when
\r
701 looking at branches (or tags) as it stops at the root
\r
702 of that branch, and gives a quick indication of changes
\r
703 made in that branch only.
\r
706 Normally you will want to leave this option unchecked.
\r
707 TortoiseGit remembers the state of the checkbox, so
\r
708 it will respect your preference.
\r
711 When the Show Log dialog is invoked from within the
\r
712 Merge dialog, the box is always checked by default.
\r
713 This is because merging is most often looking at
\r
714 changes on branches, and going back beyond the root
\r
715 of the branch does not make sense in that instance.
\r
718 Note that Git currently implements renaming
\r
719 as a copy/delete pair, so renaming a file or folder
\r
720 will also cause the log display to stop if this
\r
727 If you want to see more log messages, click the
\r
728 <guibutton>Next 100</guibutton> to retrieve the next 100 log messages.
\r
729 You can repeat this as many times as needed.
\r
732 Next to this button there is a multi-function button which remembers
\r
733 the last option you used it for. Click on the arrow to see the other
\r
737 Use <guibutton>Show Range ...</guibutton> if you want to view a specific
\r
738 range of revisions. A dialog will then prompt you to enter the start
\r
742 Use <guibutton>Show All</guibutton> if you want to see
\r
743 <emphasis>all</emphasis> log messages from HEAD right back to revision 1.
\r
748 <sect2 id="tsvn-dug-showlog-current-rev">
\r
749 <title>Current Working Copy Revision</title>
\r
751 Because the log dialog shows you the log from HEAD, not from the
\r
752 current working copy revision, it often happens that there are
\r
753 log messages shown for content which has not yet been updated
\r
754 in your working copy. To help make this clearer, the commit
\r
755 message which corresponds to the revision you have in your
\r
756 working copy is shown in bold.
\r
759 By default this only works for files. This is because the
\r
760 update revision for a folder may not correspond to the update
\r
761 revision of its content, and the only way to find the effective
\r
762 update revision for the folder is to crawl the working copy.
\r
763 This can be a slow operation for large working copies so if
\r
764 you want to enable this feature you must create a
\r
765 <literal>DWORD</literal> registry key with value 1 at
\r
766 <literal>HKCU\Software\TortoiseGit\RecursiveLogRev</literal>.
\r
771 <sect2 id="tsvn-dug-showlog-mergetrack">
\r
772 <title>Merge Tracking Features</title>
\r
774 <primary>merge tracking log</primary>
\r
777 Git 1.5 and later keeps a record of merges using properties.
\r
778 This allows us to get a more detailed history of merged changes.
\r
779 For example, if you develop a new feature on a branch and then merge
\r
780 that branch back to trunk, the feature development will show up on
\r
781 the trunk log as a single commit for the merge, even though there
\r
782 may have been 1000 commits during branch development.
\r
784 <figure id="tsvn-dug-showlog-dia-mergetrack">
\r
785 <title>The Log Dialog Showing Merge Tracking Revisions</title>
\r
786 <graphic fileref="../images/LogMergeTrack.png"/>
\r
789 If you want to see the detail of which revisions were merged as part
\r
790 of that commit, use the <guilabel>Include merged revisions</guilabel>
\r
791 checkbox. This will fetch the log messages again, but will also
\r
792 interleave the log messages from revisions which were merged.
\r
793 Merged revisions are shown in grey because they represent changes
\r
794 made on a different part of the tree.
\r
797 Of course, merging is never simple! During feature development on the
\r
798 branch there will probably be occasional merges back from trunk to
\r
799 keep the branch in sync with the main line code. So the merge history
\r
800 of the branch will also include another layer of merge history.
\r
801 These different layers are shown in the log dialog using indentation
\r
807 <sect2 id="tsvn-dug-showlog-4">
\r
808 <title>Changing the Log Message and Author</title>
\r
810 <primary>edit log/author</primary>
\r
813 <primary>revision properties</primary>
\r
816 <primary>revprops</primary>
\r
819 Revision properties are completely different from the Git
\r
820 properties of each item. Revprops are descriptive items which are
\r
821 associated with one specific revision number in the repository,
\r
822 such as log message, commit date and committer name (author).
\r
825 Sometimes you might want to change a log message you once entered,
\r
826 maybe because there's a spelling error in it or you want to
\r
827 improve the message or change it for other reasons. Or you want to
\r
828 change the author of the commit because you forgot to set up
\r
829 authentication or...
\r
832 Git lets you change revision properties any time you want.
\r
833 But since such changes can't be
\r
834 undone (those changes are not versioned) this feature is disabled
\r
835 by default. To make this work, you must set up a pre-revprop-change
\r
836 hook. Please refer to the chapter on
\r
837 <ulink url="http://svnbook.red-bean.com/en/1.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks">
\r
838 <citetitle>Hook Scripts</citetitle>
\r
840 in the Git Book for details about how to do that.
\r
841 Read <xref linkend="tsvn-repository-hooks"/> to find some further
\r
842 notes on implementing hooks on a Windows machine.
\r
845 Once you've set up your server with the required hooks, you can
\r
846 change the author and log message (or any other revprop) of any revision,
\r
847 using the context menu from the top pane of the Log dialog.
\r
848 You can also edit a log message using the context menu for the middle pane.
\r
852 Because Git's revision properties are not versioned, making
\r
853 modifications to such a property (for example, the
\r
854 <literal>svn:log</literal> commit
\r
855 message property) will overwrite the previous value of that
\r
856 property <emphasis>forever</emphasis>.
\r
861 <sect2 id="tsvn-dug-showlog-filter">
\r
862 <title>Filtering Log Messages</title>
\r
864 <primary>filter</primary>
\r
867 If you want to restrict the log messages to show only those
\r
868 you are interested in rather than scrolling through a list
\r
869 of hundreds, you can use the filter controls at the top of
\r
870 the Log Dialog. The start and end date controls allow you
\r
871 to restrict the output to a known date range. The search
\r
872 box allows you to show only messages which contain a
\r
876 Click on the search icon to select which information you want
\r
877 to search in, and to choose <emphasis>regex</emphasis> mode.
\r
878 Normally you will only need a simple text search, but if you
\r
879 need to more flexible search terms, you can use regular expressions.
\r
880 If you hover the mouse over the box, a tooltip will give hints
\r
881 on how to use the regex functions.
\r
882 You can also find online documentation and a tutorial at
\r
883 <ulink url="http://www.regular-expressions.info/">
\r
884 <citetitle>http://www.regular-expressions.info/</citetitle>
\r
886 The filter works by checking whether your filter string matches
\r
887 the log entries, and then only those entries which <emphasis>match</emphasis>
\r
888 the filter string are shown.
\r
891 To make the filter show all log entries that do <emphasis>not</emphasis>
\r
892 match the filter string, start the string with an exclamation mark ('!').
\r
893 For example, a filter string <literal>!username</literal> will only
\r
894 show those entries which were not committed by <literal>username</literal>.
\r
897 Note that these filters act on the messages already retrieved.
\r
898 They do not control downloading of messages from the repository.
\r
901 You can also filter the path names in the bottom pane using the
\r
902 <guilabel>Hide unrelated changed paths</guilabel> checkbox.
\r
903 Related paths are those which contain the path used to display
\r
904 the log. If you fetch the log for a folder, that means anything
\r
905 in that folder or below it. For a file it means just that one file.
\r
906 The checkbox is tristate: you can show all paths, grey out the
\r
907 unrelated ones, or hide the unrelated paths completely.
\r
910 Sometimes your working practices will require log messages to follow
\r
911 a particular format, which means that the text describing the changes
\r
912 is not visible in the abbreviated summary shown in the top pane.
\r
913 The property <literal>tsvn:logsummary</literal> can be used to
\r
914 extract a portion of the log message to be shown in the top pane.
\r
915 Read <xref linkend="tsvn-dug-propertypage-tsvn-props"/> to find
\r
916 out how to use this property.
\r
919 <title>No Log Formatting from Repository Browser</title>
\r
921 Because the formatting depends upon accessing Git
\r
922 properties, you will only see the results when using a checked
\r
923 out working copy. Fetching properties remotely is a slow operation,
\r
924 so you will not see this feature in action from the repo browser.
\r
928 <sect2 id="tsvn-dug-showlog-5">
\r
929 <?dbhh topicname="HIDD_STATGRAPH"?>
\r
930 <title>Statistical Information</title>
\r
932 <primary>statistics</primary>
\r
935 The <guibutton>Statistics</guibutton> button brings up a box
\r
936 showing some interesting information about the revisions
\r
937 shown in the Log dialog. This shows how many authors have
\r
938 been at work, how many commits they have made, progress
\r
939 by week, and much more. Now you can see at a glance who
\r
940 has been working hardest and who is slacking ;-)
\r
942 <sect3 id="tsvn-dug-showlog-stats-1">
\r
943 <title>Statistics Page</title>
\r
945 This page gives you all the numbers you can think of,
\r
946 in particular the period and number of revisions covered,
\r
947 and some min/max/average values.
\r
950 <sect3 id="tsvn-dug-showlog-stats-2">
\r
951 <title>Commits by Author Page</title>
\r
953 <figure id="tsvn-dug-showlog-stats-dia-2">
\r
954 <title>Commits-by-Author Histogram</title>
\r
955 <graphic fileref="../images/StatsByAuthor.png"/>
\r
957 This graph shows you which authors have been active on the
\r
958 project as a simple histogram, stacked histogram or
\r
960 <figure id="tsvn-dug-showlog-stats-dia-3">
\r
961 <title>Commits-by-Author Pie Chart</title>
\r
962 <graphic fileref="../images/StatsByAuthPie.png"/>
\r
966 Where there are a few major authors and many minor contributors,
\r
967 the number of tiny segments can make the graph more difficult to
\r
968 read. The slider at the bottom allows you to set a threshold
\r
969 (as a percentage of total commits) below which any activity is
\r
970 grouped into an <emphasis>Others</emphasis> category.
\r
973 <sect3 id="tsvn-dug-showlog-stats-3">
\r
974 <title>Commits by date Page</title>
\r
976 <figure id="tsvn-dug-showlog-stats-dia-4">
\r
977 <title>Commits-by-date Graph</title>
\r
978 <graphic fileref="../images/StatsByDate.png"/>
\r
980 This page gives you a graphical representation of project
\r
981 activity in terms of number of commits <emphasis>and</emphasis>
\r
982 author. This gives some idea of when a project is being worked
\r
983 on, and who was working at which time.
\r
986 When there are several authors, you will get many lines on the
\r
987 graph. There are two views available here: <emphasis>normal</emphasis>,
\r
988 where each author's activity is relative to the base line, and
\r
989 <emphasis>stacked</emphasis>, where each author's activity is
\r
990 relative to the line underneath.
\r
991 The latter option avoids the lines crossing over, which can make
\r
992 the graph easier to read, but less easy to see one author's output.
\r
996 By default the analysis is case-sensitive, so users
\r
997 <literal>PeterEgan</literal> and <literal>PeteRegan</literal>
\r
998 are treated as different authors. However, in many cases user names
\r
999 are not case-sensitive, and are sometimes entered inconsistently,
\r
1000 so you may want <literal>DavidMorgan</literal> and
\r
1001 <literal>davidmorgan</literal> to be treated as the same person.
\r
1002 Use the <guilabel>Authors case insensitive</guilabel> checkbox
\r
1003 to control how this is handled.
\r
1006 Note that the statistics cover the same period as the
\r
1007 Log dialog. If that is only displaying one revision
\r
1008 then the statistics will not tell you very much.
\r
1012 <sect2 id="tsvn-dug-showlog-cache">
\r
1013 <?dbhh topicname="HIDD_GOOFFLINE"?>
\r
1014 <title>Offline Mode</title>
\r
1016 If the server is not reachable, and you have log caching enabled
\r
1017 you can use the log dialog and revision graph in offline mode.
\r
1018 This uses data from the cache, which allows you to continue working
\r
1019 although the information may not be up-to-date or even complete.
\r
1023 <sect2 id="tsvn-dug-showlog-refresh">
\r
1024 <title>Refreshing the View</title>
\r
1026 If you want to check the repository again for newer log messages,
\r
1027 you can simply refresh the view using <keycap>F5</keycap>. If you
\r
1028 are using the log cache (enabled by default), this will check the
\r
1029 repository for newer messages and fetch only the new ones.
\r
1033 If you are using the log cache and you think the message content
\r
1034 or author may have changed, you can use <keycap>Shift-F5</keycap>
\r
1035 or <keycap>Ctrl-F5</keycap> to re-fetch the displayed messages from
\r
1036 the server and update the log cache. Note that this only affects
\r
1037 messages currently shown and does not invalidate the entire cache
\r
1038 for that repository.
\r
OSDN Git Service
