<para>\r
Search log messages for the text you enter. This searches\r
the log messages that you entered and also the action summaries\r
- created by Subversion (shown in the bottom pane). The search\r
+ created by Git (shown in the bottom pane). The search\r
is not case sensitive.\r
</para>\r
</listitem>\r
<term>Show properties</term>\r
<listitem>\r
<para>\r
- View the Subversion properties for the selected item.\r
+ View the Git properties for the selected item.\r
</para>\r
</listitem>\r
</varlistentry>\r
to differences. What's the difference?\r
</para>\r
<para>\r
- Subversion uses revision numbers to mean 2 different things.\r
+ Git uses revision numbers to mean 2 different things.\r
A revision generally represents the state of the repository at\r
a point in time, but it can also be used to represent the changeset\r
which created that revision, eg. <quote>Done in r1234</quote> means \r
<para>\r
If you select two revisions N and M, the context menu will offer\r
to show the <emphasis>difference</emphasis> between those two\r
- revisions. In Subversion terms this is\r
+ revisions. In Git terms this is\r
<literal>diff -r M:N</literal>.\r
</para>\r
<para>\r
If you select a single revision N, the context menu will offer\r
to show the <emphasis>changes</emphasis> made in that revision.\r
- In Subversion terms this is <literal>diff -r N-1:N</literal>\r
+ In Git terms this is <literal>diff -r N-1:N</literal>\r
or <literal>diff -c N</literal>.\r
</para>\r
<para>\r
of the branch does not make sense in that instance.\r
</para>\r
<para>\r
- Note that Subversion currently implements renaming\r
+ Note that Git currently implements renaming\r
as a copy/delete pair, so renaming a file or folder\r
will also cause the log display to stop if this\r
option is checked.\r
<primary>merge tracking log</primary>\r
</indexterm>\r
<para>\r
- Subversion 1.5 and later keeps a record of merges using properties.\r
+ Git 1.5 and later keeps a record of merges using properties.\r
This allows us to get a more detailed history of merged changes.\r
For example, if you develop a new feature on a branch and then merge\r
that branch back to trunk, the feature development will show up on\r
<primary>revprops</primary>\r
</indexterm>\r
<para>\r
- Revision properties are completely different from the Subversion\r
+ Revision properties are completely different from the Git\r
properties of each item. Revprops are descriptive items which are\r
associated with one specific revision number in the repository,\r
such as log message, commit date and committer name (author).\r
authentication or...\r
</para>\r
<para>\r
- Subversion lets you change revision properties any time you want.\r
+ Git lets you change revision properties any time you want.\r
But since such changes can't be\r
undone (those changes are not versioned) this feature is disabled\r
by default. To make this work, you must set up a pre-revprop-change\r
<ulink url="http://svnbook.red-bean.com/en/1.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks">\r
<citetitle>Hook Scripts</citetitle>\r
</ulink>\r
- in the Subversion Book for details about how to do that.\r
+ in the Git Book for details about how to do that.\r
Read <xref linkend="tsvn-repository-hooks"/> to find some further\r
notes on implementing hooks on a Windows machine.\r
</para>\r
</para>\r
<warning>\r
<para>\r
- Because Subversion's revision properties are not versioned, making \r
+ Because Git's revision properties are not versioned, making \r
modifications to such a property (for example, the\r
<literal>svn:log</literal> commit \r
message property) will overwrite the previous value of that \r
<tip>\r
<title>No Log Formatting from Repository Browser</title>\r
<para>\r
- Because the formatting depends upon accessing subversion\r
+ Because the formatting depends upon accessing Git\r
properties, you will only see the results when using a checked\r
out working copy. Fetching properties remotely is a slow operation,\r
so you will not see this feature in action from the repo browser.\r
OSDN Git Service
