This tool, to be used before committing your work, should help you locate problems in translation files. Please consider it as work-in-progress, as we are still working on it.
First of all, it will help you find missing accelerators - Luebbe's translation status page shows counts but not strings themselves, so the table below will help you fix these problems.
The analysis also includes some other useful lists, it checks for instance for correct new line styles, untranslated strings and spelling mistakes. As we prefer to err on the side of caution, you may find a lot of false positives. Anyway I hope this will help you improve the quality of your translation.
Oto
Please follow this link if you think you may help with translation.
-> TortoiseSVN translation
You can upload file for check before you make actual commit, so you can fix errors in one commit.
Make sure you are going to check translation against proper branch.
Last update: September 05 2010 17:08 CET (GMT+1/GMT+2(DST))
Go to STABLE.
 Language |
 GUI check |
 DOC |
 Author(s) |
||||||||
 Flag |
 PAR!! |
 ACC! |
 NLS |
 UNT |
 FUZ |
ESC |
 Note |
 |
 |
||
| Indonesian |  |
 1 |
3 |
815 |
608 |
1 |
815/608 | 7 | Zaenal Mutaqin, Thomas Edwin Santosa, Evan Allrich | ||
This test is necessary to pass or you can expect crashing of TSVN - specially true when you use longer type as is in English like %s instead of %d, %ld instead of %d, etc. Also having more parameters lead to crash TSVN. When TSVN not crash, the information is still wrong. For example number instead of text.
| Index | Line | English | Line | Native |
| 1 | 5477 | Let's say you check out a working copy of http://sounds.red-bean.com/repos sounds\n http://graphics.red-bean.com/repos/fast%20graphics \"quick graphs\"\n -r21 http://svn.red-bean.com/repos/skin-maker skins/toolkit\n |
7213(Fuzzy) | Katakanlah Anda melakukan check out copy pekerjaan sounds http://sounds.red-bean.com/repos\n quick_graphs http://graphics.red-bean.com/repos/fast%20graphics\n skins/toolkit -r21 http://svn.red-bean.com/repos/skin-maker\n |
Total:1
This is accessibility test. Passing this test is recommended. If you are interesting in more details about accelerator key overlapping I may enable such test for your language, but in fact there not too much to do against it. According Luebbe and Stefan there is no problem about it you just have to use accelerator more time to select element and then use enter or space for activate button.
PASS
This tests if new line style from pot match localized new line style. This test may have false positives when English text has new line style inconsistence. Using more lines for Native when English use just one is also alowed for most of translation even here reported.
| Index | Line | English | Line | Native |
| 1 | Assuming your repository is located in <filename>c:\\repos\\TestRepo</filename>, and your server is called <filename>localhost</filename>, enter: <screen>\n svn://localhost/repos/TestRepo\n </screen> when prompted by the repo browser. |
1463 | Beranggapan repositori Anda ditempatkan dalam <filename>c:\\repos\\TestRepo</filename>, dan server Anda disebut <filename>localhost</filename>, masukkan: <screen>\n svn://localhost/repos/TestRepo\n </screen> ketika ditanya oleh repo browser. |
|
| 2 | You can also increase security and save time entering URLs with svnserve by using the --root switch to set the root location and restrict access to a specified directory on the server: <screen>\n svnserve.exe --daemon --root drive:\\path\\to\\repository\\root\n </screen> Using the previous test as a guide, svnserve would now run as: <screen>\n svnserve.exe --daemon --root c:\\repos\n </screen> And in TortoiseSVN our repo-browser URL is now shortened to: <screen>\n svn://localhost/TestRepo\n </screen> Note that the --root switch is also needed if your repository is located on a different partition or drive than the location of svnserve on your server. |
1467 | Anda juga bisa meningkatkan keamanan dan menghemat waktu memasukan Url dengan svnserve dengan menggunakan saklar --root untuk men-set akar lokasi dan membatasi akses ke direktori tertentu pada server: <screen>\n svnserve.exe --daemon --root drive:\\path\\to\\repository\\root\n </screen> Menggunakan tes sebelumnya sebagai bimbingan, sekarang svnserve berjalan seperti: <screen>\n svnserve.exe --daemon --root c:\\repos\n </screen> Dan dalam TortoiseSVN Url repo-browser kita sekarang diperpendek menjadi: <screen>\n svn://localhost/TestRepo\n </screen> Catatan bahwa saklar --root juga diperlukan jika repositori Anda ditempatkan pada partisi atau drive berbeda dengan lokasi svnserve pada server Anda. |
|
| 3 | 11583 | translator-credits | 11583 | Zaenal Mutaquin\n Thomas Edwin Santosa\n Evan Allrich\n Edwin Elisia |
Total:3
This tests if all strings has been translated. Translated mean that there in native string set. If English and native are same it is not marked as not translated, this just can happen.
| Index | Line | English | Line |
| 1 | 15 | @@image: 'images/svn_move.png'; md5=THIS FILE DOESN'T EXIST | 33 |
| 2 | 77 | TortoiseSVN is a free open-source Windows client for the time machine. |
|
| 3 | 105 | TortoiseSVN integrates seamlessly into the Windows shell (i.e. the explorer). This means you can keep working with the tools you're already familiar with. And you do not have to change into a different application each time you need the functions of version control. | |
| 4 | 109 | And you are not limited to using the Windows Explorer; TortoiseSVN's context menus work in many other file managers, and also in the File/Open dialog which is common to most standard Windows applications. You should, however, bear in mind that TortoiseSVN is intentionally developed as an extension for the Windows Explorer. Thus it is possible that in other applications the integration is not as complete and e.g. the icon overlays may not be shown. | |
| 5 | 121 | Graphical User Interface | |
| 6 | 125 | When you list the changes to a file or folder, you can click on a revision to see the comments for that commit. You can also see a list of changed files - just double click on a file to see exactly what changed. | |
| 7 | 129 | The commit dialog lists all the items that will be included in a commit, and each item has a checkbox so you can choose which items you want to include. Unversioned files can also be listed, in case you forgot to add that new file. | |
| 8 | 193 | License | |
| 9 | 197 | TortoiseSVN is an Open Source project developed under the GNU General Public License (GPL). It is free to download and free to use, either personally or commercially, on any number of PCs. | |
| 10 | 201 | Although most people just download the installer, you also have full read access to the source code of this program. You can browse it on this link |
|
| 11 | 205 | Development | |
| 12 | 209 | Both TortoiseSVN and Subversion are developed by a community of people who are working on those projects. They come from different countries all over the world, working together to create great software. | |
| 13 | 217 | In 2002, Tim Kemp found that Subversion was a very good version control system, but it lacked a good GUI client. The idea for a Subversion client as a Windows shell integration was inspired by the similar client for CVS named TortoiseCVS. Tim studied the source code of TortoiseCVS and used it as a base for TortoiseSVN. He then started the project, registered the domain |
|
| 14 | 221 | Around that time, Stefan Küng was looking for a good and free version control system and found Subversion and the source for TortoiseSVN. Since TortoiseSVN was still not ready for use, he joined the project and started programming. He soon rewrote most of the existing code and started adding commands and features, up to a point where nothing of the original code remained. | |
| 15 | 225 | As Subversion became more stable it attracted more and more users who also started using TortoiseSVN as their Subversion client. The user base grew quickly (and is still growing every day). That's when Lübbe Onken offered to help out with some nice icons and a logo for TortoiseSVN. He now takes care of the website and manages the many translations. | |
| 16 | 245 | for the hard work to get TortoiseSVN to what it is now, and his leadership of the project | |
| 17 | 261 | for maintaining the documentation | |
| 18 | 265 | Stefan Fuhrmann | |
| 19 | 269 | for the log cache and revision graph | |
| 20 | 293 | for the patches, bug reports and new ideas, and for helping others by answering questions on our mailing list | |
| 21 | 309 | This book is written for computer-literate folk who want to use Subversion to manage their data, but prefer to use a GUI client rather than a command line client. TortoiseSVN is a windows shell extension and it is assumed that the user is familiar with the windows explorer and how to use it. | |
| 22 | 313 | This |
|
| 23 | 317 | The |
|
| 24 | 389 | Where extreme care has to be taken. Data corruption or other nasty things may occur if these warnings are ignored. | |
| 25 | 398 | This section is aimed at people who would like to find out what TortoiseSVN is all about and give it a test drive. It explains how to install TortoiseSVN and set up a local repository, and it walks you through the most commonly used operations. | |
| 26 | 410 | TortoiseSVN runs on Windows XP or higher and is available in both 32-bit and 64-bit flavours. If you are running 64-bit Windows you may want to install both versions. | |
| 27 | 414 | Support for Windows 98, Windows ME and Windows NT4 was dropped in version 1.2.0 and Windows 2000 support was dropped in 1.7.0. You can still download and install older versions if you need them. | |
| 28 | 426 | TortoiseSVN comes with an easy to use installer. Double click on the installer file and follow the instructions. The installer will take care of the rest. Don't forget to reboot after installation. | |
| 29 | 430 | You need Administrator privileges to install TortoiseSVN. | 556 |
| 30 | 434 | Language packs are available which translate the TortoiseSVN user interface into many different languages. Please check |
|
| 31 | 438 | If you encounter any problems during or after installing TortoiseSVN please refer to our online FAQ at |
|
| 32 | 442 | Basic Concepts | |
| 33 | 446 | Before we get stuck into working with some real files, it is important to get an overview of how subversion works and the terms that are used. | |
| 34 | 457 | Subversion uses a central database which contains all your version-controlled files with their complete history. This database is referred to as the |
|
| 35 | 466 | This is where you do the real work. Every developer has his own working copy, sometimes known as a sandbox, on his local PC. You can pull down the latest version from the repository, work on it locally without affecting anyone else, then when you are happy with the changes you made commit them back to the repository. | |
| 36 | 470 | A Subversion working copy does not contain the history of the project, but it does keep a copy of the files as they exist in the repository before you started making changes. This means that it is easy to check exactly what changes you have made. | |
| 37 | 479 | You also need to know where to find TortoiseSVN because there is not much to see from the Start Menu. This is because TortoiseSVN is a Shell extension, so first of all, start Windows Explorer. Right click on a folder in Explorer and you should see some new entries in the context menu like this: |
|
| 38 | 483 | Go for a Test Drive | |
| 39 | 487 | This section shows you how to try out some of the most commonly used features on a small test repository. Naturally it doesn't explain everything - this is just the Quick Start Guide after all. Once you are up and running you should take the time to read the rest of this user guide, which takes you through things in much more detail. It also explains more about setting up a proper Subversion server. | |
| 40 | 491 | Creating a Repository | |
| 41 | 495 | For a real project you will have a repository set up somewhere safe and a Subversion server to control it. For the purposes of this tutorial we are going to use Subversion's local repository feature which allows direct access to a repository created on your hard drive without needing a server at all. | |
| 42 | 499 | First create a new empty directory on your PC. It can go anywhere, but in this tutorial we are going to call it |
|
| 43 | 503 | The local repository feature is very useful for test and evaluation but unless you are working as a sole developer on one PC you should always use a proper Subversion server. It is tempting in a small company to avoid the work of setting up a server and just access your repository on a network share. Don't ever do that. You will lose data. Read |
|
| 44 | 507 | Importing a Project | |
| 45 | 516 | Now we have a repository, but it is completely empty at the moment. Let's assume I have a set of files in |
|
| 46 | 520 | The other important feature of this dialog is the Import the Widget1 project. Click on |
|
| 47 | 524 | Checking out a Working Copy | |
| 48 | 528 | Now that we have a project in our repository, we need to create a working copy to use for day-to-day work. Note that the act of importing a folder does not automatically turn that folder into a working copy. The Subversion term for creating a fresh working copy is |
|
| 49 | 532 | You will notice that the appearance of this folder is different from our original folder. Every file has a green check mark in the bottom left corner. These are TortoiseSVN's status icons which are only present in a working copy. The green state indicates that the file is unchanged from the version in the repository. | |
| 50 | 536 | Making Changes | |
| 51 | 540 | Time to get to work. In the |
|
| 52 | 544 | File Difference Viewer | |
| 53 | 548 | But what are the changes? Right click on one of the changed files and select |
|
| 54 | 552 | OK, so we are happy with the changes, let's update the repository. This action is referred to as a |
|
| 55 | 556 | Adding More Files | |
| 56 | 560 | As the project develops you will need to add new files - let's say you add some new features in |
|
| 57 | 564 | Now when you go to commit the folder, the new file shows up as |
|
| 58 | 568 | Viewing the Project History | |
| 59 | 572 | The Log Dialog | |
| 60 | 576 | One of the most useful features of TortoiseSVN is the Log dialog. This shows you a list of all the commits you made to a file or folder, and shows those detailed commit messages that you entered ;-) |
|
| 61 | 580 | The top pane shows a list of revisions committed along with the start of the commit message. If you select one of these revisions, the middle pane will show the full log message for that revision and the bottom pane will show a list of changed files and folders. | |
| 62 | 584 | Each of these panes has a context menu which provides you with lots more ways of using the information. In the bottom pane you can |
|
| 63 | 588 | Undoing Changes | |
| 64 | 592 | One feature of all revision control systems is that they let you undo changes that you made previously. As you would expect, TortoiseSVN makes this easy to access. | |
| 65 | 596 | If you want to get rid of changes that you have not yet committed and reset your file to the way it was before you started editing, |
|
| 66 | 600 | If you want to undo the effects of a particular revision, start with the Log dialog and find the offending revision. Select |
|
| 67 | 604 | Moving On ... | |
| 68 | 608 | This guide has given you a very quick tour of some of TortoiseSVN's most important and useful features, but of course there is far more that we haven't covered. We strongly recommend that you take the time to read the rest of this manual, especially |
|
| 69 | 612 | We have taken a lot of trouble to make sure that it is both informative and easy to read, but we recognise that there is a lot of it! Take your time and don't be afraid to try things out on a test repository as you go along. The best way to learn is by using it. | |
| 70 | 1115 | You will also be asked whether you want to create a directory structure within the repository. Find out about layout options in |
|
| 71 | 1119 | TortoiseSVN will set a custom folder icon when it creates a repository so you can identify local repositories more easily. If you create a repository using the official command line client this folder icon is not assigned. | |
| 72 | 1123 | TortoiseSVN no longer offers the option to create BDB repositories, although you can still use the command line client to create them. FSFS repositories are generally easier for you to maintain, and also makes it easier for us to maintain TortoiseSVN due to compatibility issues between the different BDB versions. | 1358 |
| 73 | 1127 | TortoiseSVN does not support |
|
| 74 | 1131 | Of course we also recommend that you don't use |
1366 |
| 75 | 1163 | Accessing a Repository on a Network Share | 1406 |
| 76 | 1171 | Although in theory it is possible to put a FSFS repository on a network share and have multiple users access it using |
1415 |
| 77 | 1175 | Firstly you are giving every user direct write access to the repository, so any user could accidentally delete the entire repository or make it unusable in some other way. | 1419 |
| 78 | 1179 | Secondly not all network file sharing protocols support the locking that Subversion requires, so you may find your repository gets corrupted. It may not happen straight away, but one day two users will try to access the repository at the same time. | 1423 |
| 79 | 1183 | Thirdly the file permissions have to be set just so. You may just about get away with it on a native Windows share, but SAMBA is particularly difficult. | 1427 |
| 80 | 1187 | 1431 | |
| 81 | 1208 | Because this layout is so commonly used, when you create a new repository using TortoiseSVN, it will also offer to create the directory structure for you. | |
| 82 | 1258 | import this structure into the repository via a |
|
| 83 | 1262 | So if you haven't already created a basic folder structure inside your repository you should do that now. There are two ways to achieve this. If you simply want to create a |
1555 |
| 84 | 1315 | These hook scripts are executed by the server that hosts the repository. TortoiseSVN also allows you to configure client side hook scripts that are executed locally upon certain events. See |
1645 |
| 85 | 1323 | Overriding Hooks | 1666 |
| 86 | 1327 | If a hook script rejects your commit then its decision is final. But you can build an override mechanism into the script itself using the You didn't say the magic word:-) |
1670 |
| 87 | 1483 | To install svnserve as a native windows service, execute the following command all on one line to create a service which is automatically started when windows starts. sc create svnserve binpath= \"c:\\svnserve\\svnserve.exe --service\n --root c:\\repos\" displayname= \"Subversion\" depend= tcpip\n start= auto\n sc create svnserve binpath= \"\n \\\"C:\\Program Files\\Subversion\\bin\\svnserve.exe\\\"\n --service --root c:\\repos\" displayname= \"Subversion\"\n depend= tcpip start= auto\n sc description svnserve \"Subversion server (svnserve)\"\n |
|
| 88 | 1543 | The Cyrus Simple Authentication and Security Layer is open source software written by Carnegie Mellon University. It adds generic authentication and encryption capabilities to any network protocol, and as of Subversion 1.5 and later, both the svnserve server and TortoiseSVN client know how to make use of this library. | 2038 |
| 89 | 1547 | For a more complete discussion of the options available, you should look at the Subversion book in the section |
2042 |
| 90 | 1555 | To activate specific SASL mechanisms on the server, you'll need to do three things. First, create a use-sasl = true\n |
2051 |
| 91 | 1559 | Second, create a file called |
2058 |
| 92 | 1563 | Thirdly, create two new registry entries to tell SASL where to find things. Create a registry key named |
2062 |
| 93 | 1567 | Edit the pwcheck_method: auxprop\n auxprop_plugin: sasldb\n mech_list: DIGEST-MD5\n sasldb_path: C:\\TortoiseSVN\\sasldb\n |
2066 |
| 94 | 1571 | If svnserve was already running, you will need to restart it to ensure it reads the updated configuration. | 2076 |
| 95 | 1575 | Now that everything is set up, all you need to do is create some users and passwords. To do this you need the saslpasswd2 -c -f C:\\TortoiseSVN\\sasldb -u realm username\n |
2080 |
| 96 | 1579 | You can list the usernames stored in the database using the |
2087 |
| 97 | 1587 | To enable or disable different levels of encryption, you can set two values in your repository's [sasl]\n use-sasl = true\n min-encryption = 128\n max-encryption = 256\n |
2095 |
| 98 | 1591 | The |
2105 |
| 99 | 1607 | A basic method for setting up your server is given in SSH. |
2125 |
| 100 | 1852 | You can get those three files directly from our source repository at |
|
| 101 | 1928 | NTLM | 2682 |
| 102 | 1952 | The SSPI authentication is only enabled for SSL secured connections (https). If you're only using normal http connections to your server, it won't work. | 2752 |
| 103 | 1956 | To enable SSL on your server, see the chapter: |
2756 |
| 104 | 2012 | Even though Apache 2.2.x has OpenSSL support, it is not activated by default. You need to activate this manually. | 2887 |
| 105 | 2016 | In the apache config file, uncomment the lines: #LoadModule ssl_module modules/mod_ssl.so\n #Include conf/extra/httpd-ssl.conf\n SSLMutex \"file:C:/Program Files/Apache Software Foundation/\\\n Apache2.2/logs/ssl_mutex\"\n SSLMutex default\n |
2891 |
| 106 | 2076 | Using client certificates with virtual SSL hosts | 3048 |
| 107 | 2080 | Sent to the TortoiseSVN mailing list by Nigel Green. Thanks! | 3052 |
| 108 | 2084 | In some server configurations you may need to setup a single server containing 2 virtual SSL hosts: The first one for public web access, with no requirement for a client certificate. The second one to be secure with a required client certificate, running a Subversion server. | 3056 |
| 109 | 2088 | Adding an |
3060 |
| 110 | 2092 | The solution is to add the following directive to the virtual host directory that you want to lock down for Subversion: SSLRequire %{SSL_CLIENT_VERIFY} eq \"SUCCESS\"\n |
3064 |
| 111 | 2096 | To summarise, the relevant lines of the Apache configuration are: SSLVerifyClient Optional\n \n ### Virtual host configuration for the PUBLIC host\n ### (not requiring a certificate)\n \n <VirtualHost 127.0.0.1:443>\n <Directory \"pathtopublicfileroot\">\n </Directory>\n </VirtualHost>\n \n ### Virtual host configuration for SUBVERSION\n ### (requiring a client certificate)\n <VirtualHost 127.0.0.1:443>\n <Directory \"subversion host root path\">\n SSLRequire %{SSL_CLIENT_VERIFY} eq \"SUCCESS\"\n </Directory>\n \n <Location /svn>\n DAV svn\n SVNParentPath /pathtorepository\n </Location>\n </VirtualHost>\n |
|
| 112 | 2159 | right-click | 3177 |
| 113 | 2171 | Some commands which are very rarely used are only available in the extended context menu. To bring up the extended context menu, hold down the |
3191 |
| 114 | 2183 | If you are using Windows 2000 you will find that the context menus are shown as plain text, without the menu icons shown above. We are aware that this was working in previous versions, but Microsoft has changed the way its icon handlers work for Vista, requiring us to use a different display method which unfortunately does not work on Windows 2000. | 3205 |
| 115 | 2285 | If you want to clear authentication for one realm only then you will have to dig into those directories, find the file which contains the information you want to clear and delete the file. | 3336 |
| 116 | 2289 | Some people like to have the authentication data deleted when they log off Windows, or on shutdown. The way to do that is to use a shutdown script to delete the @echo off\n rmdir /s /q \"%APPDATA%\\Subversion\\auth\"\n |
3340 |
| 117 | 2297 | Maximizing Windows | 3353 |
| 118 | 2301 | maximize | 3357 |
| 119 | 2305 | Many of TortoiseSVN's dialogs have a lot of information to display, but it is often useful to maximize only the height, or only the width, rather than maximizing to fill the screen. As a convenience, there are shortcuts for this on the |
3361 |
| 120 | 2332 | If you are importing into an existing repository which already contains some projects, then the repository structure will already have been decided. If you are importing data into a new repository, then it is worth taking the time to think about how it will be organised. Read |
3394 |
| 121 | 2336 | There is no way to select files and folders to include, aside from using the global ignore settings. | 3398 |
| 122 | 2340 | The folder imported does not become a working copy. You have to do a checkout to copy the files back from the server. | 3402 |
| 123 | 2348 | This section describes the Subversion import command, which was designed for importing a directory hierarchy into the repository in one shot. Although it does the job, it has several shortcomings: |
3412 |
| 124 | 2368 | In this dialog you have to enter the URL of the repository location where you want to import your project. It is very important to realise that the local folder you are importing does not itself appear in the repository, only its content. For example if you have a structure: C:\\Projects\\Widget\\source\n C:\\Projects\\Widget\\doc\n C:\\Projects\\Widget\\images\n |
3442 |
| 125 | 2468 | Checkout the entire tree, including all child folders and sub-folders. | 3570 |
| 126 | 2472 | Immediate children, including folders | 3574 |
| 127 | 2476 | Checkout the specified directory, including all files and child folders, but do not populate the child folders. | 3578 |
| 128 | 2480 | Only file children | 3582 |
| 129 | 2484 | Checkout the specified directory, including all files but do not checkout any child folders. | 3586 |
| 130 | 2492 | Checkout the directory only. Do not populate it with files or child folders. | 3596 |
| 131 | 2502 | Retain the depth specified in the working copy. This option is not used in the checkout dialog, but it is the default in all other dialogs which have a depth setting. | 3607 |
| 132 | 2506 | Exclude | 3611 |
| 133 | 2510 | Used to reduce working copy depth after a folder has already been populated. This option is only available in the |
3615 |
| 134 | 2514 | You can choose the |
3619 |
| 135 | 2518 | If you check out a sparse working copy (i.e., by choosing something other than |
3623 |
| 136 | 2522 | In windows explorer, |
|
| 137 | 2526 | In the check for modifications dialog, first click on the button |
3633 |
| 138 | 2530 | This feature is very useful when you only want to checkout parts of a large tree, but you want the convenience of updating a single working copy. Suppose you have a large tree which has sub-folders |
3637 |
| 139 | 2534 | Checkout the parent folder with depth Only this itemYou now have an empty top level folder. |
3641 |
| 140 | 2542 | Right click on |
3651 |
| 141 | 2546 | Repeat the same process for |
3655 |
| 142 | 2550 | Navigate to |
3659 |
| 143 | 2562 | Using an older server | 3675 |
| 144 | 2566 | Pre-1.5 servers do not understand the working copy depth request, so they cannot always deal with requests efficiently. The command will still work, but an older server may send all the data, leaving the client to filter out what is not required, which may mean a lot of network traffic. If possible you should upgrade your server to 1.5. | 3679 |
| 145 | 2663 | You can select or deselect items by clicking on the checkbox to the left of the item. For directories you can use |
3805 |
| 146 | 2671 | By default when you commit changes, any locks that you hold on files are released automatically after the commit succeeds. If you want to keep those locks, make sure the |
3814 |
| 147 | 2708 | The commit dialog supports Subversion's changelist feature to help with grouping related files together. Find out about this feature in |
3854 |
| 148 | 2712 | Excluding Items from the Commit List | 3858 |
| 149 | 2716 | Sometimes you have versioned files that change frequently but that you really don't want to commit. Sometimes this indicates a flaw in your build process - why are those files versioned? should you be using template files? But occasionally it is inevitable. A classic reason is that your IDE changes a timestamp in the project file every time you build. The project file has to be versioned as it includes all the build settings, but it doesn't need to be committed just because the timestamp changed. | 3862 |
| 150 | 2720 | To help out in awkward cases like this, we have reserved a changelist called |
3866 |
| 151 | 2748 | Getting the regex just right can be tricky, so to help you sort out a suitable expression there is a test dialog which allows you to enter an expression and then type in filenames to test it against. Start it from the command prompt using the command |
|
| 152 | 2752 | You can re-use previously entered log messages. Just click on |
3901 |
| 153 | 2756 | You can clear all stored commit messages from the |
3905 |
| 154 | 2764 | Another way to insert the paths into the log message is to simply drag the files from the file list onto the edit control. | 3915 |
| 155 | 3008 | A file conflict occurs when two or more developers have changed the same few lines of a file. As Subversion knows nothing of your project, it leaves resolving the conflicts to the developers. Whenever a conflict is reported, you should open the file in question, and search for lines starting with the string <<<<<<< filename\n your changes\n =======\n code merged from repository\n >>>>>>> revision\n |
|
| 156 | 3032 | A tree conflict occurs when a developer moved/renamed/deleted a file or folder, which another developer either also has moved/renamed/deleted or just modified. There are many different situations that can result in a tree conflict, and all of them require different steps to resolve the conflict. | 4274 |
| 157 | 3036 | When a file is deleted locally in Subversion, the file is also deleted from the local file system, so even if it is part of a tree conflict it cannot show a conflicted overlay and you cannot right click on it to resolve the conflict. Use the |
4278 |
| 158 | 3069 | Developer B now has to choose whether to keep Developer A's changes. In the case of a file rename, he can merge the changes to |
4311 |
| 159 | 3073 | The conflict edit dialog offers to merge changes if it can find the original file of the renamed |
4315 |
| 160 | 3131 | To merge her local changes with the reshuffle, Developer B must first find out to what filename the conflicted file |
4377 |
| 161 | 3135 | If Developer B decides that A's changes were wrong then she must choose the |
4381 |
| 162 | 3163 | To resolve this conflict, Developer B has to find out to what filename the conflicted file |
4413 |
| 163 | 3168 | Then developer B has to decide which new filename of |
4418 |
| 164 | 3181 | Developer A working on trunk modifies |
4431 |
| 165 | 3185 | Developer B working on a branch moves |
4435 |
| 166 | 3199 | A merge of developer A's trunk changes to developer B's branch working copy results in a tree conflict: |
4449 |
| 167 | 3203 | To resolve this conflict, Developer B has to mark the file as resolved in the conflict editor dialog, which will remove it from the conflict list. She then has to decide whether to copy the missing file |
4453 |
| 168 | 3207 | Note that if you copy the missing file from the repository and then mark as resolved, your copy will be removed again. You have to resolve the conflict first. | 4457 |
| 169 | 3220 | Developer B working on a branch modifies |
4470 |
| 170 | 3224 | There is an equivalent case for folder moves, but it is not yet detected in Subversion 1.6 ... | 4474 |
| 171 | 3228 | Developer A working on trunk moves parent folder |
4478 |
| 172 | 3232 | Developer B working on a branch modifies |
4482 |
| 173 | 3244 | To merge her local changes with the reshuffle, Developer B must first find out to what filename the conflicted file |
4494 |
| 174 | 3248 | If Developer B decides that A's changes were wrong then she must choose the |
4498 |
| 175 | 3256 | Developer B working on a branch moves |
4506 |
| 176 | 3272 | To resolve this conflict, Developer B has to find out to what filename the conflicted file |
4522 |
| 177 | 3276 | Other tree conflicts | |
| 178 | 3280 | There are other cases which are labelled as tree conflicts simply because the conflict involves a folder rather than a file. For example if you add a folder with the same name to both trunk and branch and then try to merge you will get a tree conflict. If you want to keep the folder from the merge target, just mark the conflict as resolved. If you want to use the one in the merge source then you need to SVN delete the one in the target first and run the merge again. If you need anything more complicated then you have to resolve manually. | |
| 179 | 3358 | Now that there are more Tortoise clients around (TortoiseCVS, TortoiseHG, ...) the icon limit becomes a real problem. To work around this, the TortoiseSVN project introduced a common shared icon set, loaded as a DLL, which can be used by all Tortoise clients. Check with your client provider to see if this has been integrated yet :-) | 4628 |
| 180 | 3362 | For a description of how icon overlays correspond to Subversion status and other technical details, read |
4632 |
| 181 | 3382 | The additional columns in the Windows Explorer are not available on Vista, since Microsoft decided to not allow such columns for |
4657 |
| 182 | 3463 | At the bottom of the dialog you can see a summary of the range of repository revisions in use in your working copy. These are the |
4759 |
| 183 | 3503 | You can see changelists in several places, but the most important ones are the commit dialog and the check-for-modifications dialog. Let's start in the check-for-modifications dialog after you have worked on several features and many files. When you first open the dialog, all the changed files are listed together. Suppose you now want to organise things and group those files according to feature. | 4807 |
| 184 | 3511 | Once you have created a changelist you can drag and drop items into it, either from another changelist, or from Windows Explorer. Dragging from Explorer can be useful as it allows you to add items to a changelist before the file is modified. You could do that from the check-for-modifications dialog, but only by displaying all unmodified files. | 4816 |
| 185 | 3523 | On XP, there is a context menu when you right click on a group heading which gives you the choice to check or uncheck all group entries. On Vista however the context menu is not necessary. Click on the group header to select all entries, then check one of the selected entries to check all. | 4830 |
| 186 | 3527 | TortoiseSVN reserves one changelist name for its own use, namely |
4834 |
| 187 | 3615 | The top pane has an |
4944 |
| 188 | 3619 | 4948 | |
| 189 | 3631 | 4964 | |
| 190 | 3693 | Open / Open with... | 5049 |
| 191 | 3706 | Blame the file up to the selected revision. (files only). | 5066 |
| 192 | 3734 | If you want to undo an earlier change permanently, use |
5106 |
| 193 | 3747 | If your working copy is in an unmodified state, after you perform this action your working copy will show as modified. If you already have local changes, this command will merge the |
5123 |
| 194 | 3751 | What is happening internally is that Subversion performs a reverse merge of all the changes made after the selected revision, undoing the effect of those previous commits. | 5127 |
| 195 | 3755 | If after performing this action you decide that you want to |
5131 |
| 196 | 3759 | If you simply want to see what a file or folder looked like at an earlier revision, use |
5135 |
| 197 | 3772 | What is happening internally is that Subversion performs a reverse merge of that one revision, undoing its effect from a previous commit. | 5152 |
| 198 | 3776 | You can |
5156 |
| 199 | 3784 | Merge the selected revision(s) into a different working copy. 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 copy 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. | 5166 |
| 200 | 3816 | View and edit any revision property, not just log message and author. Refer to |
5207 |
| 201 | 3821 | Copy to clipboard | 5212 |
| 202 | 3838 | 5232 | |
| 203 | 3866 | Show differences as unified diff | 5269 |
| 204 | 3890 | You can also choose to merge the selected revisions to another working copy, as described above. | 5299 |
| 205 | 3894 | If all selected revisions have the same author, you can edit the author of all those revisions in one go. | 5303 |
| 206 | 3906 | Show changes made in the selected revision for the selected file. | |
| 207 | 3931 | Opens the Blame dialog, allowing you to blame up to the selected revision. | 5354 |
| 208 | 3959 | Show the revision log for the selected single file, including merged changes. Find out more in |
5391 |
| 209 | 3971 | You may notice that sometimes we refer to changes and other times to differences. What's the difference? | 5405 |
| 210 | 3975 | Subversion uses revision numbers 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. Done in r1234means that the changes committed in r1234 implement feature X. To make it clearer which sense is being used, we use two different terms. |
5409 |
| 211 | 3979 | If you select two revisions N and M, the context menu will offer to show the |
5413 |
| 212 | 3983 | If you select a single revision N, the context menu will offer to show the |
5417 |
| 213 | 3987 | The bottom pane shows the files changed in all selected revisions, so the context menu always offers to show |
5421 |
| 214 | 4039 | Because the log dialog shows you the log from HEAD, not from the current working copy revision, it often happens that there are log messages shown for content which has not yet been updated in your working copy. To help make this clearer, the commit message which corresponds to the revision you have in your working copy is shown in bold. | 5487 |
| 215 | 4043 | When you show the log for a folder the revision highlighted is the highest revision found anywhere within that folder, which requires a crawl of the working copy. The crawl takes place within a separate thread so as not to delay showing the log, but as a result highlighting for folders may not appear immediately. | 5491 |
| 216 | 4047 | Merge Tracking Features | 5495 |
| 217 | 4055 | Subversion 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. | 5505 |
| 218 | 4059 | The Log Dialog Showing Merge Tracking Revisions | 5509 |
| 219 | 4063 | If you want to see the detail of which revisions were merged as part of that commit, use the |
5513 |
| 220 | 4067 | 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. | 5517 |
| 221 | 4087 | Revision properties are completely different from the Subversion 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). | 5543 |
| 222 | 4119 | Click on the search icon to select which information you want to search in, and to choose |
|
| 223 | 4123 | Simple sub-string search works in a manner similar to a search engine. Strings to search for are separated by spaces, and all strings must match. You can use a leading Alice Bob -Eve\n !Alice Bob\n !-Alice -Bob\n \"Alice and Bob\"\n Alice and Bob \"\"\n \"Alice says \"\"hi\"\" to Bob\"\n Alice says \"hi\" to Bob |
|
| 224 | 4127 | Describing the use of regular expression searches is beyond the scope of this manual, but you can find online documentation and a tutorial at |
|
| 225 | 4135 | You can also filter the path names in the bottom pane using the |
|
| 226 | 4139 | 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 |
5607 |
| 227 | 4147 | Because the formatting depends upon accessing subversion properties, you will only see the results when using a checked out working copy. Fetching properties remotely is a slow operation, so you will not see this feature in action from the repo browser. | 5617 |
| 228 | 4215 | Offline Mode | 5703 |
| 229 | 4219 | Go Offline Dialog | 5707 |
| 230 | 4223 | 5711 | |
| 231 | 4227 | Offline for now | 5715 |
| 232 | 4231 | Complete the current operation in offline mode, but retry the repository next time log data is requested. | 5719 |
| 233 | 4235 | Permanently offline | 5723 |
| 234 | 4239 | Remain in offline mode until a repository check is specifically requested. See |
5727 |
| 235 | 4243 | Cancel | 5731 |
| 236 | 4247 | If you don't want to continue the operation with possibly stale data, just cancel. | 5735 |
| 237 | 4255 | The |
5745 |
| 238 | 4260 | Refreshing the View | 5750 |
| 239 | 4264 | If you want to check the server again for newer log messages, you can simply refresh the view using |
5754 |
| 240 | 4268 | If you are using the log cache and you think the message content or author may have changed, you can use |
5758 |
| 241 | 4321 | If you want to see the difference between the last committed revision and your working copy, assuming that the working copy hasn't been modified, just right click on the file. Then select |
5825 |
| 242 | 4377 | If you have configured a third party diff tool, you can use |
5896 |
| 243 | 4381 | Line-end and Whitespace Options | 5900 |
| 244 | 4385 | Sometimes in the life of a project you might change the line endings from |
5904 |
| 245 | 4389 | 5908 | |
| 246 | 4393 | 5912 | |
| 247 | 4397 | 5916 | |
| 248 | 4401 | 5920 | |
| 249 | 4405 | Naturally, any line with changed content is always included in the diff. | 5924 |
| 250 | 4433 | You can export a |
5958 |
| 251 | 4453 | If the list of filenames is very long, you can use the search box to reduce the list to filenames containing specific text. Note that a simple text search is used, so if you want to restrict the list to C source files you should enter |
5983 |
| 252 | 4489 | When the images are overlaid, the relative intensity of the images (alpha blend) is controlled by a slider control at the left side. You can click anywhere in the slider to set the blend directly, or you can drag the slider to change the blend interactively. |
6030 |
| 253 | 4493 | The button above the slider toggles between 0% and 100% blends, and if you double click the button, the blend toggles automatically every second until you click the button again. This can be useful when looking for multiple small changes. | 6034 |
| 254 | 4497 | Sometimes you want to see a difference rather than a blend. You might have the image files for two revisions of a printed circuit board and want to see which tracks have changed. If you disable alpha blend mode, the difference will be shown as an |
6038 |
| 255 | 4648 | Copying/Moving/Renaming Files and Folders | 6228 |
| 256 | 4674 | It often happens that you already have the files you need in another project in your repository, and you simply want to copy them across. You could simply copy the files and add them as described above, but that would not give you any history. And if you subsequently fix a bug in the original files, you can only merge the fix automatically if the new copy is related to the original in Subversion. | 6260 |
| 257 | 4678 | The easiest way to copy files and folders from within a working copy is to use the right-drag menu. When you |
6264 |
| 258 | 4682 | You can also copy or move versioned files within a working copy, or between two working copies, using the familiar cut-and-paste method. Use the standard Windows |
6268 |
| 259 | 4694 | You can also use the repository browser to locate content you want, and copy it into your working copy directly from the repository, or copy between two locations within the repository. Refer to |
6284 |
| 260 | 4702 | Whilst you can copy or move files and folders |
6294 |
| 261 | 4706 | If you are uncertain whether two URLs on the same server refer to the same or different repositories, use the repo browser to open one URL and find out where the repository root is. If you can see both locations in one repo browser window then they are in the same repository. | 6298 |
| 262 | 4806 | You should not include path information in your pattern. The pattern matching is intended to be used against plain file names and folder names. If you want to ignore all |
6424 |
| 263 | 4908 | Another way of moving or copying files is to use the Windows copy/cut commands. Select the files you want to copy, right-click and choose |
|
| 264 | 4924 | Changing case in a filename | 6574 |
| 265 | 4932 | Making case-only changes to a filename is tricky with Subversion on Windows, because for a short time during a rename, both filenames have to exist. As Windows has a case-insensitive file system, this does not work using the usual Rename command. | 6584 |
| 266 | 4973 | Dealing with filename case conflicts | 6635 |
| 267 | 4981 | This sometimes happens when two people commit, from separate working copies, files which happen to have the same name, but with a case difference. It can also happen when files are committed from a system with a case-sensitive file system, like Linux. | 6645 |
| 268 | 5050 | If you want to undo a deletion or a rename, you need to use Revert on the parent folder as the deleted item does not exist for you to right-click on. | 6725 |
| 269 | 5063 | Since revert is sometimes used to clean up a working copy, there is an extra button which allows you to delete unversioned items as well. When you click this button another dialog comes up listing all the unversioned items, which you can then select for deletion. | 6741 |
| 270 | 5079 | When you revert changes you may find that the operation takes a lot longer than you expect. This is because the modified version of the file is sent to the recycle bin, so you can retrieve your changes if you reverted by mistake. However, if your recycle bin is full, Windows takes a long time to find a place to put the file. The solution is simple: either empty the recycle bin or deactivate the |
6761 |
| 271 | 5154 | expand keywords | 6858 |
| 272 | 5158 | Date of last known commit. This is based on information obtained when you update your working copy. It does |
6862 |
| 273 | 5162 | Revision of last known commit. | 6866 |
| 274 | 5166 | Author who made the last known commit. | 6870 |
| 275 | 5174 | A compressed combination of the previous four keywords. | 6880 |
| 276 | 5178 | Subversion supports CVS-like keyword expansion which can be used to embed filename and revision information within the file itself. Keywords currently supported are: |
6884 |
| 277 | 5226 | Edit properties at HEAD revision | |
| 278 | 5230 | Because properties are versioned, you cannot edit the properties of previous revisions. If you look at properties from the log dialog, or from a non-HEAD revision in the repository browser, you will see a list of properties and values, but no edit controls. | |
| 279 | 5250 | If you want to add properties to a tree recursively, follow the steps above, then in the property dialog select each property in turn, click on |
6965 |
| 280 | 5254 | The Import file format is binary and proprietary to TortoiseSVN. Its only purpose is to transfer properties using Import and Export, so there is no need to edit these files. | 6969 |
| 281 | 5274 | auto-props | 6994 |
| 282 | 5282 | You can edit the subversion configuration file to enable this feature on your client. The |
7004 |
| 283 | 5286 | An alternative method is to set the |
7008 |
| 284 | 5290 | Whichever method you choose, you should note that auto-props are only applied to files at the time they are added to the repository. Auto-props will never change the properties of files which are already versioned. | 7012 |
| 285 | 5294 | If you want to be absolutely sure that new files have the correct properties applied, you should set up a repository pre-commit hook to reject commits where the required properties are not set. | 7016 |
| 286 | 5342 | Subversion allows you to set autopropswhich will be applied to newly added or imported files, based on the file extension. This depends on every client having set appropriate autoprops in their subversion configuration file. |
7078 |
| 287 | 5346 | If there is a conflict between the local autoprops and |
7082 |
| 288 | 5362 | The property |
7103 |
| 289 | 5366 | The value of the |
7107 |
| 290 | 5370 | An example: [SUMMARY]in the log message and use that as the summary. |
7111 |
| 291 | 5374 | The property |
7115 |
| 292 | 5378 | The regular expression must match the whole reference, not just the revision number. The revision number is extracted from the matched reference string automatically. | 7119 |
| 293 | 5382 | If this property is not set, a default regular expression is used to link revision references. | 7123 |
| 294 | 5423 | When you add new sub-folders to a working copy using TortoiseSVN, any project properties present in the parent folder will automatically be added to the new child folder too. | |
| 295 | 5428 | Limitations Using the Repository Browser | |
| 296 | 5432 | Fetching properties remotely is a slow operation, so some of the features described above will not work in the repository browser as they do in a working copy. | |
| 297 | 5436 | When you add a property using the repo browser, only the standard |
|
| 298 | 5440 | Properties cannot be set or deleted recursively using the repo browser. | |
| 299 | 5444 | Project properties will |
|
| 300 | 5448 | ||
| 301 | 5452 | Although TortoiseSVN's project properties are extremely useful, they only work with TortoiseSVN, and some will only work in newer versions of TortoiseSVN. If people working on your project use a variety of Subversion clients, or possibly have old versions of TortoiseSVN, you may want to use repository hooks to enforce project policies. project properties can only help to implement a policy, they cannot enforce it. | 7179 |
| 302 | 5481 | URLs must be properly escaped or they will not work, e.g. you must replace each space with |
7228 |
| 303 | 5485 | If you want the local path to include spaces or other special characters, you can enclose it in double quotes, or you can use the |
7232 |
| 304 | 5501 | The format shown here was introduced in Subversion 1.5. You may also see the older format which has the same information in a different order. The new format is preferred as it supports several useful features described below, but it will not work on older clients. The differences are shown in the |
7254 |
| 305 | 5506 | If the external project is in the same repository, any changes you make there will be included in the commit list when you commit your main project. | |
| 306 | 5515 | If you use absolute URLs in |
7270 |
| 307 | 5519 | To avoid such problems, Subversion clients version 1.5 and higher support relative external URLs. Four different methods of specifying a relative URL are supported. In the following examples, assume we have two repositories: one at |
7274 |
| 308 | 5523 | Relative to parent directory | 7278 |
| 309 | 5527 | These URLs always begin with the string ../../widgets/foo common/foo-widget\n |
7282 |
| 310 | 5531 | Note that the URL is relative to the URL of the directory with the |
7289 |
| 311 | 5539 | These URLs always begin with the string ^/widgets/foo common/foo-widget\n |
7299 |
| 312 | 5543 | You can easily refer to other repositories with the same ^/../repos-2/hammers/claw common/claw-hammer\n |
7306 |
| 313 | 5547 | Relative to scheme | 7313 |
| 314 | 5551 | URLs beginning with the string //example.com/svn/repos-1/widgets/foo common/foo-widget\n |
7317 |
| 315 | 5555 | Relative to the server's hostname | 7324 |
| 316 | 5559 | URLs beginning with the string /svn/repos-1/widgets/foo common/foo-widget\n |
7328 |
| 317 | 5563 | You can also specify a peg revision after the URL if required, e.g. |
7335 |
| 318 | 5579 | As of Subversion 1.6 you can add single file externals to your working copy using the same syntax as for folders. However, there are some restrictions. | 7355 |
| 319 | 5583 | The path to the file external must place the file in an existing versioned folder. In general it makes most sense to place the file directly in the folder that has |
7359 |
| 320 | 5587 | The URL for a file external must be in the same repository as the URL that the file external will be inserted into; inter-repository file externals are not supported. | 7363 |
| 321 | 5591 | A file external behaves just like any other versioned file in many respects, but they cannot be moved or deleted using the normal commands; the |
7367 |
| 322 | 5595 | File externals support incomplete in Subversion 1.6 | 7371 |
| 323 | 5599 | In subversion 1.6 it is not possible to remove a file external from your working copy once you have added it, even if you delete the |
7375 |
| 324 | 5685 | You can also create a branch or tag without having a working copy. To do that, open the repository browser. You can there drag folders to a new location. You have to hold down the |
7495 |
| 325 | 5689 | You can also drag a folder with the right mouse button. Once you release the mouse button you can choose from the context menu whether you want the folder to be moved or copied. Of course to create a branch or tag you must copy the folder, not move it. | 7499 |
| 326 | 5693 | Yet another way is from the log dialog. You can show the log dialog for e.g. trunk, select a revision (either the HEAD revision at the very top or an earlier revision), right-click and choose |
7503 |
| 327 | 5772 | The next point to note is that merging |
7605 |
| 328 | 5792 | What you are asking Subversion to do is this: Calculate the changes necessary to get [FROM] revision 1 of branch A [TO] revision 7 of branch A, and apply those changes to my working copy (of trunk or branch B). |
7631 |
| 329 | 5797 | Reintegrate a branch | 7636 |
| 330 | 5805 | This is a special case of the tree merge described below, and it requires only the URL to merge from (normally) your development branch. It uses the merge-tracking features of Subversion to calculate the correct revision ranges to use, and perform additional checks which ensure that the branch has been fully updated with trunk changes. This ensures that you don't accidentally undo work that others have committed to trunk since you last synchronized changes. | 7646 |
| 331 | 5809 | After the merge, all branch development has been completely merged back into the main development line. The branch is now redundant and can be deleted. | 7650 |
| 332 | 5813 | Once you have performed a reintegrate merge you should not continue to use it for development. The reason for this is that if you try to resynchronize your existing branch from trunk later on, merge tracking will see your reintegration as a trunk change that has not yet been merged into the branch, and will try to merge the branch-to-trunk merge back into the branch! The solution to this is simply to create a new branch from trunk to continue the next phase of your development. | 7654 |
| 333 | 5821 | This is a more general case of the reintegrate method. What you are asking Subversion to do is: Calculate the changes necessary to get [FROM] the head revision of the trunk [TO] the head revision of the branch, and apply those changes to my working copy (of the trunk).The net result is that trunk now looks exactly like the branch. |
7664 |
| 334 | 5825 | If your server/repository does not support merge-tracking then this is the only way to merge a branch back to trunk. Another use case occurs when you are using vendor branches and you need to merge the changes following a new vendor drop into your trunk code. For more information read the chapter on |
7668 |
| 335 | 5837 | The Merge Wizard - Select Revision Range | 7683 |
| 336 | 5845 | In the |
7693 |
| 337 | 5849 | There is an important difference in the way a revision range is specified with TortoiseSVN compared to the command line client. The easiest way to visualise it is to think of a fence with posts and fence panels. | 7697 |
| 338 | 5853 | With the command line client you specify the changes to merge using two fence postrevisions which specify the |
7701 |
| 339 | 5857 | With TortoiseSVN you specify the changeset to merge using fence panels. The reason for this becomes clear when you use the log dialog to specify revisions to merge, where each revision appears as a changeset. |
7705 |
| 340 | 5861 | If you are merging revisions in chunks, the method shown in the subversion book will have you merge 100-200 this time and 200-300 next time. With TortoiseSVN you would merge 100-200 this time and 201-300 next time. | 7709 |
| 341 | 5865 | This difference has generated a lot of heat on the mailing lists. We acknowledge that there is a difference from the command line client, but we believe that for the majority of GUI users it is easier to understand the method we have implemented. | 7713 |
| 342 | 5873 | If you want to merge changes back |
7723 |
| 343 | 5881 | If you are using the merge tracking features of Subversion, you do not need to remember which revisions have already been merged - Subversion will record that for you. If you leave the revision range blank, all revisions which have not yet been merged will be included. Read |
7733 |
| 344 | 5889 | Click |
7742 |
| 345 | 5897 | The Merge Wizard - Reintegrate Merge | 7752 |
| 346 | 5901 | 7756 | |
| 347 | 5909 | There are some conditions which apply to a reintegrate merge. Firstly, the server must support merge tracking. The working copy must be of depth infinite (no sparse checkouts), and it must not have any local modifications, switched items or items that have been updated to revisions other than HEAD. All changes to trunk made during branch development must have been merged across to the branch (or marked as having been merged). The range of revisions to merge will be calculated automatically. | 7766 |
| 348 | 5917 | two trees | 7775 |
| 349 | 5921 | The Merge Wizard - Tree Merge | 7779 |
| 350 | 5925 | 7783 | |
| 351 | 5949 | This page of the wizard lets you specify advanced options, before starting the merge process. Most of the time you can just use the default settings. | 7816 |
| 352 | 5953 | You can specify the depth to use for the merge, i.e. how far down into your working copy the merge should go. The depth terms used are described in |
7820 |
| 353 | 5961 | You can specify the way that line ending and whitespace changes are handled. These options are described in |
7830 |
| 354 | 5965 | The checkbox marked |
7834 |
| 355 | 5969 | If you are using merge tracking and you want to mark a revision as having been merged, without actually doing the merge here, check the |
7838 |
| 356 | 5973 | Now everything is set up, all you have to do is click on the |
|
| 357 | 5977 | The merge progress dialog shows each stage of the merge, with the revision ranges involved. This may indicate one more revision than you were expecting. For example if you asked to merge revision 123 the progress dialog will report Merging revisions 122 through 123. To understand this you need to remember that Merge is closely related to Diff. The merge process works by generating a list of differences between two points in the repository, and applying those differences to your working copy. The progress dialog is simply showing the start and end points for the diff. |
7848 |
| 358 | 5985 | The merge is now complete. It's a good idea to have a look at the merge and see if it's as expected. Merging is usually quite complicated. Conflicts often arise if the branch has drifted far from the trunk. | 7858 |
| 359 | 5993 | If your server and all clients are running Subversion 1.5 or higher, the merge tracking facility will record the revisions merged and avoid a revision being merged more than once. This makes your life much simpler as you can simply merge the entire revision range each time and know that only new revisions will actually be merged. | 7868 |
| 360 | 6017 | You can avoid the danger of merging the same revision twice (repeated merge problem). Once a revision is marked as having been merged, future merges which include that revision in the range will skip over it. | 7901 |
| 361 | 6021 | When you merge a branch back into trunk, the log dialog can show you the branch commits as part of the trunk log, giving better traceability of changes. | 7905 |
| 362 | 6025 | When you show the log dialog from within the merge dialog, revisions already merged are shown in grey. | 7909 |
| 363 | 6029 | When showing blame information for a file, you can choose to show the original author of merged revisions, rather than the person who did the merge. | 7913 |
| 364 | 6033 | You can mark revisions as |
7917 |
| 365 | 6037 | Subversion 1.5 introduced facilities for merge tracking. When you merge changes from one tree into another, the revision numbers merged are stored and this information can be used for several different purposes. |
7921 |
| 366 | 6041 | Merge tracking information is stored in the |
7925 |
| 367 | 6049 | Handling Conflicts during Merge | 7935 |
| 368 | 6061 | Merging does not always go smoothly. Sometimes there is a conflict, and if you are merging multiple ranges, you generally want to resolve the conflict before merging of the next range starts. TortoiseSVN helps you through this process by showing the |
7951 |
| 369 | 6065 | Choosing |
|
| 370 | 6069 | Normally you will want to look at the conflicts and resolve them yourself. In that case, choose the |
|
| 371 | 6073 | The last option is to postpone resolution and continue with merging. You can choose to do that for the current conflicted file, or for all files in the rest of the merge. However, if there are further changes in that file, it will not be possible to complete the merge. | 7963 |
| 372 | 6077 | It is likely that some of the changes will have merged smoothly, while other local changes conflict with changes already committed to the repository. All changes which can be merged are merged. The Merge Conflict Callback dialog gives you three different ways of handling the lines which are in conflict. |
|
| 373 | 6081 | If you do not want to use this interactive callback, there is a checkbox in the merge progress dialog |
7973 |
| 374 | 6085 | Merge a Completed Branch | 7977 |
| 375 | 6097 | If you want to merge all changes from a feature branch back to trunk, then you can use the |
7993 |
| 376 | 6101 | Feature Branch Maintenance | 7997 |
| 377 | 6105 | When you develop a new feature on a separate branch it is a good idea to work out a policy for re-integration when the feature is complete. If other work is going on in |
8001 |
| 378 | 6109 | If the feature is relatively simple and development will not take long then you can adopt a simple approach, which is to keep the branch entirely separate until the feature is complete, then merge the branch changes back into trunk. In the merge wizard this would be a simple |
8005 |
| 379 | 6113 | If the feature is going to take longer and you need to account for changes in |
8009 |
| 380 | 6125 | readonly | 8023 |
| 381 | 6377 | You can specify the way that line ending and whitespace changes are handled. These options are described in |
8343 |
| 382 | 6413 | If you need a better visual indicator of where the oldest and newest changes are, select |
8387 |
| 383 | 6417 | If you are using Merge Tracking, where lines have changed as a result of merging from another path, TortoiseBlame will show the revision and author of the last change in the original file rather than the revision where the merge took place. These lines are indicated by showing the revision and author in italics. If you do not want merged lines shown in this way, uncheck the |
8391 |
| 384 | 6486 | The repository browser looks very similar to the Windows explorer, except that it is showing the content of the repository at a particular revision rather than files on your computer. In the left pane you can see a directory tree, and in the right pane are the contents of the selected directory. At the top of the Repository Browser Window you can enter the URL of the repository and the revision you want to browse. | 8482 |
| 385 | 6490 | Just like Windows explorer, you can click on the column headings in the right pane if you want to set the sort order. And as in explorer there are context menus available in both panes. | 8486 |
| 386 | 6498 | Show the revision log for that file, or show a graph of all revisions so you can see where the file came from. | 8496 |
| 387 | 6502 | Blame the file, to see who changed which line and when. | 8500 |
| 388 | 6506 | Delete or rename the file. | 8504 |
| 389 | 6510 | Make a copy of the file, either to a different part of the repository, or to a working copy rooted in the same repository. | 8508 |
| 390 | 6514 | View/Edit the file's properties. | 8512 |
| 391 | 6518 | The context menu for a file allows you to: |
8516 |
| 392 | 6522 | Show the revision log for that folder, or show a graph of all revisions so you can see where the folder came from. | 8520 |
| 393 | 6526 | Export the folder to a local unversioned copy on your hard drive. | 8524 |
| 394 | 6530 | Checkout the folder to produce a local working copy on your hard drive. | 8528 |
| 395 | 6542 | Delete or rename the folder. | 8544 |
| 396 | 6546 | Make a copy of the folder, either to a different part of the repository, or to a working copy rooted in the same repository. This can also be used to create a branch/tag without the need to have a working copy checked out. | 8548 |
| 397 | 6554 | Mark the folder for comparison. A marked folder is shown in bold. | 8558 |
| 398 | 6562 | The context menu for a folder allows you to: |
8568 |
| 399 | 6570 | If you select multiple folders in the right pane, you can checkout all of them at once into a common parent folder. | 8578 |
| 400 | 6578 | You can use |
8587 |
| 401 | 6630 | The good news is that if you are using log caching, you only have to suffer this delay once. After that, log data is held locally. Log caching is enabled in TortoiseSVN's settings. | 8657 |
| 402 | 6638 | Added or copied items | 8667 |
| 403 | 6642 | Items which have been added, or created by copying another file/folder are shown using a rounded rectangle. The default colour is green. Tags and trunks are treated as a special case and use a different shade, depending on the |
8671 |
| 404 | 6658 | Renamed items are also shown using an octagon, but the default colour is blue. | 8693 |
| 405 | 6666 | The graph is normally restricted to showing branch points, but it is often useful to be able to see the respective HEAD revision for each branch too. If you select |
8702 |
| 406 | 6674 | If you invoked the revision graph from a working copy, you can opt to show the BASE revision on the graph using |
8712 |
| 407 | 6682 | If you invoked the revision graph from a working copy, you can opt to show an additional node representing your modified working copy using |
8722 |
| 408 | 6694 | Each revision graph node represents a revision in the repository where something changed in the tree you are looking at. Different types of node can be distinguished by shape and colour. The shapes are fixed, but colours can be set using |
8737 |
| 409 | 6702 | The default view (grouping off) places the nodes such that their vertical position is in strict revision order, so you have a visual cue for the order in which things were done. Where two nodes are in the same column the order is very obvious. When two nodes are in adjacent columns the offset is much smaller because there is no need to prevent the nodes from overlapping, and as a result the order is a little less obvious. Such optimisations are necessary to keep complex graphs to a reasonable size. Please note that this ordering uses the |
8747 |
| 410 | 6706 | Changing the View | 8751 |
| 411 | 6714 | The default behavior (grouping off) has all rows sorted strictly by revision. As a result, long-living branches with sparse commits occupy a whole column for only a few changes and the graph becomes very broad. | 8761 |
| 412 | 6718 | This mode groups changes by branch, so that there is no global revision ordering: Consecutive revisions on a branch will be shown in (often) consecutive lines. Sub-branches, however, are arranged in such a way that later branches will be shown in the same column above older branches to keep the graph slim. As a result, a given row may contain changes from different revisions. | 8765 |
| 413 | 6722 | Oldest on top | 8769 |
| 414 | 6726 | Normally the graph shows the oldest revision at the bottom, and the tree grows upwards. Use this option to grow down from the top instead. | 8773 |
| 415 | 6730 | Align trees on top | 8777 |
| 416 | 6734 | When a graph is broken into several smaller trees, the trees may appear either in natural revision order, or aligned at the bottom of the window, depending on whether you are using the |
8781 |
| 417 | 6738 | Reduce cross lines | 8785 |
| 418 | 6742 | If the layout of the graph has produced a lot of crossing lines, use this option to clean it up. This may make the layout columns appear in less logical places, for example in a diagonal line rather than a column, and the graph may require a larger area to draw. | 8789 |
| 419 | 6746 | Differential path names | 8793 |
| 420 | 6750 | Long path names can take a lot of space and make the node boxes very large. Use this option to show only the changed part of a path, replacing the common part with dots. E.g. if you create a branch |
8797 |
| 421 | 6758 | This does just what you expect and shows every revision where something (in the tree that you are graphing) has changed. For long histories this can produce a truly huge graph. | 8807 |
| 422 | 6766 | This ensures that the latest revision on every branch is always shown on the graph. | 8816 |
| 423 | 6770 | Exact copy sources | 8820 |
| 424 | 6774 | When a branch/tag is made, the default behaviour is to show the branch as taken from the last node where a change was made. Strictly speaking this is inaccurate since the branches are often made from the current HEAD rather than a specific revision. So it is possible to show the more correct (but less useful) revision that was used to create the copy. Note that this revision may be younger than the HEAD revision of the source branch. | 8824 |
| 425 | 6778 | Fold tags | 8828 |
| 426 | 6782 | When a project has many tags, showing every tag as a separate node on the graph takes a lot of space and obscures the more interesting development branch structure. At the same time you may need to be able to access the tag content easily so that you can compare revisions. This option hides the nodes for tags and shows them instead in the tooltip for the node that they were copied from. A tag icon on the right side of the source node indicates that tags were made. | 8832 |
| 427 | 6786 | Hide deleted paths | 8836 |
| 428 | 6790 | Hides paths which are no longer present at the HEAD revision of the repository, e.g. deleted branches. | 8840 |
| 429 | 6794 | Hide unchanged branches | 8844 |
| 430 | 6798 | Hides branches where no changes were committed to the respective file or sub-folder. This does not necessarily indicate that the branch was not used, just that no changes were made to |
8848 |
| 431 | 6806 | Marks the revision on the graph which corresponds to the update revision of the item you fetched the graph for. If you have just updated, this will be HEAD, but if others have committed changes since your last update your WC may be a few revisions lower down. The node is marked by giving it a bold outline. | 8858 |
| 432 | 6814 | If your WC contains local changes, this option draws it as a separate elliptical node, linked back to the node that your WC was last updated to. The default outline colour is red. You may need to refresh the graph using |
8868 |
| 433 | 6826 | Tree stripes | 8883 |
| 434 | 6830 | Where the graph contains several trees, it is sometimes useful to use alternating colours on the background to help distinguish between trees. | 8887 |
| 435 | 6834 | Show overview | 8891 |
| 436 | 6838 | Shows a small picture of the entire graph, with the current view window as a rectangle which you can drag. This allows you to navigate the graph more easily. Note that for very large graphs the overview may become useless due to the extreme zoom factor and will therefore not be shown in such cases. | 8895 |
| 437 | 6842 | Because a revision graph is often quite complex, there are a number of features which can be used to tailor the view the way you want it. These are available in the |
8899 |
| 438 | 6850 | To make it easier to navigate a large graph, use the overview window. This shows the entire graph in a small window, with the currently displayed portion highlighted. You can drag the highlighted area to change the displayed region. | 8909 |
| 439 | 6870 | You can also merge changes in the selected revision(s) into a different working copy. 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 copy 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. | 8934 |
| 440 | 6878 | First-time users may be surprised by the fact that the revision graph shows something that does not match the user's mental model. If a revision changes multiple copies or branches of a file or folder, for instance, then there will be multiple nodes for that single revision. It is a good practice to start with the leftmost options in the toolbar and customize the graph step-by-step until it comes close to your mental model. | 8944 |
| 441 | 6882 | All filter options try lose as little information as possible. That may cause some nodes to change their color, for instance. Whenever the result is unexpected, undo the last filter operation and try to understand what is special about that particular revision or branch. In most cases, the initially expected outcome of the filter operation would either be inaccurate or misleading. | 8948 |
| 442 | 6886 | If you want to check the server again for newer information, you can simply refresh the view using |
8952 |
| 443 | 6890 | If you are using the log cache and you think the message content or author may have changed, you should use the log dialog to refresh the messages you need. Since the revision graph works from the repository root, we would have to invalidate the entire log cache, and refilling it could take a |
8956 |
| 444 | 6894 | Pruning Trees | 8960 |
| 445 | 6898 | A large tree can be difficult to navigate and sometimes you will want to hide parts of it, or break it down into a forest of smaller trees. If you hover the mouse over the point where a node link enters or leaves the node you will see one or more popup buttons which allow you to do this. | 8964 |
| 446 | 6902 | 8968 | |
| 447 | 6906 | 8972 | |
| 448 | 6910 | 8976 | |
| 449 | 6914 | 8980 | |
| 450 | 6918 | Click on the graph background for the main context menu, which offers options to |
8984 |
| 451 | 6966 | The export dialog does not allow exporting single files, even though Subversion can. | 9044 |
| 452 | 6970 | To export single files with TortoiseSVN, you have to use the repository browser ( |
9048 |
| 453 | 6978 | If you want to export a copy of your project tree structure but containing only the files which have changed in a particular revision, or between any two revisions, use the compare revisions feature described in |
9058 |
| 454 | 6991 | Sometimes you have a working copy which you want to convert back to a normal folder without the |
9074 |
| 455 | 6995 | The answer is surprisingly simple - export the folder to itself! TortoiseSVN detects this special case and asks if you want to make the working copy unversioned. If you answer |
9078 |
| 456 | 7031 | You may be surprised to find that TortoiseSVN contacts the repository as part of this operation. All it is doing is performing some simple checks to make sure that the new URL really does refer to the same repository as the existing working copy. | 9126 |
| 457 | 7120 | You can also use relative URLs instead of absolute ones. This is useful when your issue tracker is on the same domain/server as your source repository. In case the domain name ever changes, you don't have to adjust the |
9243 |
| 458 | 7124 | If it begins with the string |
9247 |
| 459 | 7128 | A URL beginning with the string |
9251 |
| 460 | 7140 | Issue Number in Text Box | 9267 |
| 461 | 7164 | Issue Numbers Using Regular Expressions | 9299 |
| 462 | 7172 | If two expressions are set, then the first expression is used as a pre-filter to find expressions which contain bug IDs. The second expression then extracts the bare bug IDs from the result of the first regex. This allows you to use a list of bug IDs and natural language expressions if you wish. e.g. you might fix several bugs and include a string something like this: This change resolves issues #23, #24 and #25 |
9309 |
| 463 | 7180 | The first expression picks out issues #23, #24 and #25from the surrounding log message. The second regex extracts plain decimal numbers from the output of the first regex, so it will return 23, 24and 25to use as bug IDs. |
9319 |
| 464 | 7184 | Breaking the first regex down a little, it must start with the word issue, possibly capitalised. This is optionally followed by an s(more than one issue) and optionally a colon. This is followed by one or more groups each having zero or more leading whitespace, an optional comma or andand more optional space. Finally there is a mandatory #and a mandatory decimal number. |
9323 |
| 465 | 7208 | And even if you don't need the links, the issue numbers show up as a separate column in the log dialog, making it easier to find the changes which relate to a particular issue. | 9355 |
| 466 | 7222 | No Issue Tracker Information from Repository Browser | 9372 |
| 467 | 7226 | Because the issue tracker integration depends upon accessing subversion properties, you will only see the results when using a checked out working copy. Fetching properties remotely is a slow operation, so you will not see this feature in action from the repo browser unless you started the repo browser from your working copy. If you started the repo browser by entering the URL of the repository you won't see this feature. | 9376 |
| 468 | 7231 | For the same reason, project properties will not be propagated automatically when a child folder is added using the repo browser. | |
| 469 | 7235 | This issue tracker integration is not restricted to TortoiseSVN; it can be used with any Subversion client. For more information, read the full |
|
| 470 | 7239 | Getting Information from the Issue Tracker | 9386 |
| 471 | 7243 | The previous section deals with adding issue information to the log messages. But what if you need to get information from the issue tracker? The commit dialog has a COM interface which allows integration an external program that can talk to your tracker. Typically you might want to query the tracker to get a list of open issues assigned to you, so that you can pick the issues that are being addressed in this commit. | 9390 |
| 472 | 7247 | Any such interface is of course highly specific to your issue tracker system, so we cannot provide this part, and describing how to create such a program is beyond the scope of this manual. The interface definition and sample plugins in C# and C++/ATL can be obtained from the |
|
| 473 | 7251 | Example issue tracker query dialog | 9398 |
| 474 | 7255 | For illustration purposes, let's suppose that your system administrator has provided you with an issue tracker plugin which you have installed, and that you have set up some of your working copies to use the plugin in TortoiseSVN's settings dialog. When you open the commit dialog from a working copy to which the plugin has been assigned, you will see a new button at the top of the dialog. |
9402 |
| 475 | 7271 | ViewVC | 9421 |
| 476 | 7291 | Set this property to the URL of your repo viewer to view changes to a specific file in a specific revision. It must be properly URI encoded and it has to contain |
|
| 477 | 7295 | You can also use relative URLs instead of absolute ones. This is useful in case your web viewer is on the same domain/server as your source repository. In case the domain name ever changes, you don't have to adjust the |
9450 |
| 478 | 7299 | Because the repo viewer integration depends upon accessing subversion properties, you will only see the results when using a checked out working copy. Fetching properties remotely is a slow operation, so you will not see this feature in action from the repo browser unless you started the repo browser from your working copy. If you started the repo browser by entering the URL of the repository you won't see this feature. | 9460 |
| 479 | 7339 | Check for updates | |
| 480 | 7343 | TortoiseSVN will contact its download site periodically to see if there is a newer version of the program available. If there is it will show a notification link in the commit dialog. Use |
|
| 481 | 7443 | If there are some paths on your computer where you just don't want TortoiseSVN's context menu to appear at all, you can list them in the box at the bottom. | 9645 |
| 482 | 7483 | Can double-click in log list to compare with previous revision | 9695 |
| 483 | 7487 | If you frequently find yourself comparing revisions in the top pane of the log dialog, you can use this option to allow that action on double-click. It is not enabled by default because fetching the diff is often a long process, and many people prefer to avoid the wait after an accidental double-click, which is why this option is not enabled by default. | 9699 |
| 484 | 7491 | Auto-close | |
| 485 | 7511 | Always close dialogs for local operations | |
| 486 | 7515 | Local operations like adding files or reverting changes do not need to contact the repository and complete quickly, so the progress dialog is often of little interest. Select this option if you want the progress dialog to close automatically after these operations, unless there are errors. | |
| 487 | 7519 | Use recycle bin when reverting | 9733 |
| 488 | 7523 | When you revert local modifications, your changes are discarded. TortoiseSVN gives you an extra safety net by sending the modified file to the recycle bin before bringing back the pristine copy. If you prefer to skip the recycle bin, uncheck this option. | 9737 |
| 489 | 7567 | In the |
9788 |
| 490 | 7603 | Note that this setting applies only to messages that you type in on this computer. It has nothing to do with the log cache. | 9838 |
| 491 | 7619 | The normal behaviour in the commit dialog is for all modified (versioned) items to be selected for commit automatically. If you prefer to start with nothing selected and pick the items for commit manually, uncheck this box. | 9859 |
| 492 | 7631 | Show Lock dialog before locking files | 9873 |
| 493 | 7635 | When you select one or more files and then use |
9877 |
| 494 | 7639 | If you use the lock command on a folder, you are always presented with the lock dialog as that also gives you the option to select files for locking. | 9881 |
| 495 | 7643 | If your project is using the |
9885 |
| 496 | 7735 | Filter match | |
| 497 | 7739 | When using filtering in the log dialog, search terms are highlighted in the results using this colour. | |
| 498 | 7751 | Classification Patterns | 10011 |
| 499 | 7755 | The revision graph attempts to show a clearer picture of your repository structure by distinguishing between trunk, branches and tags. As there is no such classification built into Subversion, this information is extracted from the path names. The default settings assume that you use the conventional English names as suggested in the Subversion documentation, but of course your usage may vary. | 10015 |
| 500 | 7759 | Specify the patterns used to recognise these paths in the three boxes provided. The patterns will be matched case-insensitively, but you must specify them in lower case. Wild cards |
10019 |
| 501 | 7767 | Colors are used in the revision graph to indicate the node type, i.e. whether a node is added, deleted, renamed. In order to help pick out node classifications, you can allow the revision graph to blend colors to give an indication of both node type and classification. If the box is checked, blending is used. If the box is unchecked, color is used to indicate node type only. Use the color selection dialog to allocate the specific colors used. | 10029 |
| 502 | 7779 | 10045 | |
| 503 | 7787 | Items which have been deleted and not copied anywhere else in the same revision. | 10055 |
| 504 | 7795 | Items newly added, or copied (add with history). | 10065 |
| 505 | 7803 | Items deleted from one location and added in another in the same revision. | 10075 |
| 506 | 7811 | Simple modifications without any add or delete. | 10085 |
| 507 | 7819 | May be used to show the revision used as the source of a copy, even when no change (to the item being graphed) took place in that revision. | 10095 |
| 508 | 7831 | WC Node | 10111 |
| 509 | 7835 | If you opt to show an extra node for your modified working copy, attached to its last-commit revision on the graph, use this color. | 10115 |
| 510 | 7839 | WC Node Border | 10119 |
| 511 | 7843 | If you opt to show whether the working copy is modified, use this color border on the WC node when modifications are found. | 10123 |
| 512 | 7847 | Tag Nodes | 10127 |
| 513 | 7851 | Nodes classified as tags may be blended with this color. | 10131 |
| 514 | 7855 | Trunk Nodes | 10135 |
| 515 | 7859 | Nodes classified as trunk may be blended with this color. | 10139 |
| 516 | 7863 | Folded Tag Markers | 10143 |
| 517 | 7867 | If you use tag folding to save space, tags are marked on the copy source using a block in this color. | 10147 |
| 518 | 7875 | When you left click on a node to select it, the marker used to indicate selection is a block in this color. | 10157 |
| 519 | 7879 | Stripes | 10161 |
| 520 | 7883 | These colors are used when the graph is split into sub-trees and the background is colored in alternating stripes to help pick out the separate trees. | 10165 |
| 521 | 7963 | Network drives can be very slow, so by default icons are not shown for working copies located on network shares. | 10278 |
| 522 | 7971 | The |
|
| 523 | 7975 | Any path you specify here is assumed to apply recursively, so none of the child folders will show overlays either. If you want to exclude |
|
| 524 | 7983 | Users sometimes ask how these three settings interact. For any given path check the include and exclude lists, seeking upwards through the directory structure until a match is found. When the first match is found, obey that include or exclude rule. If there is a conflict, a single directory spec takes precedence over a recursive spec, then inclusion takes precedence over exclusion. | |
| 525 | 7987 | An example will help here: Exclude:\n C:\n C:\\develop\\?\n C:\\develop\\tsvn\\obj\n C:\\develop\\tsvn\\bin\n \n Include:\n C:\\develop\n |
|
| 526 | 7995 | Exclude |
10322 |
| 527 | 7999 | SUBST drives | 10326 |
| 528 | 8003 | It is often convenient to use a subst T: C:\\TortoiseSVN\\trunk\\doc\n |
10330 |
| 529 | 8007 | An easy way to work around this is to exclude the original path from showing overlays, so that the overlays show up on the |
10337 |
| 530 | 8011 | Sometimes you will exclude areas that contain working copies, which saves TSVNCache from scanning and monitoring for changes, but you still want a visual indication that such folders are versioned. The |
10341 |
| 531 | 8015 | As a special exception to this, drives |
10345 |
| 532 | 8031 | Enabled Overlay Handlers | |
| 533 | 8035 | The Settings Dialog, Icon Handlers Page | |
| 534 | 8039 | ||
| 535 | 8067 | You must specify the full path to the executable. For TortoisePlink.exe this is the standard TortoiseSVN bin directory. Use the \"C:\\Program Files\\TortoiseSVN\\bin\\TortoisePlink.exe\"\n |
10395 |
| 536 | 8075 | TortoisePlink does not have any documentation of its own because it is just a minor variant of Plink. Find out about command line parameters from the |
10407 |
| 537 | 8079 | To avoid being prompted for a password repeatedly, you might also consider using a password caching tool such as Pageant. This is also available for download from the PuTTY website. | 10411 |
| 538 | 8083 | Finally, setting up SSH on server and clients is a non-trivial process which is beyond the scope of this help file. However, you can find a guide in the TortoiseSVN FAQ listed under |
10415 |
| 539 | 8141 | You can also specify a different diff tool to use on Subversion properties. Since these tend to be short simple text strings, you may want to use a simpler more compact viewer. | 10511 |
| 540 | 8245 | Log messages (Show log dialog) | 10664 |
| 541 | 8249 | TortoiseSVN caches log messages fetched by the Show Log dialog to save time when you next show the log. If someone else edits a log message and you already have that message cached, you will not see the change until you clear the cache. Log message caching is enabled on the |
10668 |
| 542 | 8277 | TortoiseSVN keeps a log of everything written to its progress dialogs. This can be useful when, for example, you want to check what happened in a recent update command. | 10703 |
| 543 | 8281 | The log file is limited in length and when it grows too big the oldest content is discarded. By default 4000 lines are kept, but you can customize that number. | 10707 |
| 544 | 8285 | From here you can view the log file content, and also clear it. | 10711 |
| 545 | 8301 | 10732 | |
| 546 | 8305 | Enable log caching | 10736 |
| 547 | 8309 | Enables log caching whenever log data is requested. If checked, data will be retrieved from the cache when available, and any messages not in the cache will be retrieved from the server and added to the cache. | 10740 |
| 548 | 8313 | If caching is disabled, data will always be retrieved directly from the server and not stored locally. | 10744 |
| 549 | 8317 | Allow ambiguous URLs | 10748 |
| 550 | 8321 | Occasionally you may have to connect to a server which uses the same URL for all repositories. Older versions of |
10752 |
| 551 | 8325 | Allow ambiguous UUIDs | 10756 |
| 552 | 8329 | Some hosting services give all their repositories the same UUID. You may even have done this yourself by copying a repository folder to create a new one. For all sorts of reasons this is a bad idea - a UUID should be |
10760 |
| 553 | 8337 | If you are working offline, or if the repository server is down, the log cache can still be used to supply log messages already held in the cache. Of course the cache may not be up-to-date, so there are options to allow you to select whether this feature should be used. | 10770 |
| 554 | 8341 | When log data is being taken from the cache without contacting the server, the dialog using those message will show the offline state in its title bar. | 10774 |
| 555 | 8345 | Timeout before updating the HEAD revision | 10778 |
| 556 | 8349 | When you invoke the log dialog you will normally want to contact the server to check for any newer log messages. If the timeout set here is non-zero then the server will only be contacted when the timeout has elapsed since the last time contact. This can reduce server round-trips if you open the log dialog frequently and the server is slow, but the data shown may not be completely up-to-date. If you want to use this feature we suggest using a value of 300 (5 minutes) as a compromise. | 10782 |
| 557 | 8353 | Days of inactivity until small caches get removed | 10786 |
| 558 | 8357 | If you browse around a lot of repositories you will accumulate a lot of log caches. If you're not actively using them, the cache will not grow very big, so TortoiseSVN purges them after a set time by default. Use this item to control cache purging. | 10790 |
| 559 | 8361 | Maximum size of removed inactive caches | 10794 |
| 560 | 8365 | Larger caches are more expensive to reacquire, so TortoiseSVN only purges small caches. Fine tune the threshold with this value. | 10798 |
| 561 | 8369 | Maximum number of tool failures before cache removal | 10802 |
| 562 | 8373 | Occasionally something goes wrong with the caching and causes a crash. If this happens the cache is normally deleted automatically to prevent a recurrence of the problem. If you use the less stable nightly build you may opt to keep the cache anyway. | 10806 |
| 563 | 8381 | On this page you can see a list of the repositories that are cached locally, and the space used for the cache. If you select one of the repositories you can then use the buttons underneath. | 10816 |
| 564 | 8385 | Click on the |
10820 |
| 565 | 8389 | Click on the |
10824 |
| 566 | 8393 | Click on |
10828 |
| 567 | 8409 | The amount of memory required to service this cache. | 10848 |
| 568 | 8417 | The amount of disk space used for the cache. Data is compressed, so disk usage is generally fairly modest. | 10856 |
| 569 | 8425 | Shows whether the repository was available last time the cache was used. | 10866 |
| 570 | 8437 | Last head update | 10882 |
| 571 | 8441 | The last time we requested the HEAD revision from the server. | 10886 |
| 572 | 8449 | The number of different authors with messages recorded in the cache. | 10896 |
| 573 | 8457 | The number of paths listed, as you would see using |
10906 |
| 574 | 8461 | Skip ranges | 10910 |
| 575 | 8465 | The number of revision ranges which we have not fetched, simply because they haven't been requested. This is a measure of the number of holes in the cache. | 10914 |
| 576 | 8473 | The highest revision number stored in the cache. | 10924 |
| 577 | 8481 | The number of revisions stored in the cache. This is another measure of cache completeness. | 10934 |
| 578 | 8485 | 10938 | |
| 579 | 8562 | Called before the actual Subversion update or switch begins. | |
| 580 | 8571 | Called after the update, switch or checkout finishes (whether successful or not). | |
| 581 | 8576 | Pre-connect | |
| 582 | 8580 | Called before an attempt to contact the repository. Called at most once in five minutes. | |
| 583 | 8592 | Next you must specify the command line to execute, starting with the path to the hook script or executable. This could be a batch file, an executable file or any other file which has a valid windows file association, eg. a perl script. Note that the script must not be specified using a UNC path as Windows shell execute will not allow such scripts to run due to security restrictions. | |
| 584 | 8600 | A path to a temporary file which contains all the paths for which the operation was started. Each path is on a separate line in the temp file. | 11059 |
| 585 | 8604 | The depth with which the commit/update is done. | 11063 |
| 586 | 8636 | Path to a file containing the log message for the commit. The file contains the text in UTF-8 encoding. After successful execution of the start-commit hook, the log message is read back, giving the hook a chance to modify it. | 11097 |
| 587 | 8644 | Path to a file containing the error message. If there was no error, the file will be empty. | 11106 |
| 588 | 8648 | The current working directory with which the script is run. This is set to the common root directory of all affected paths. | 11110 |
| 589 | 8656 | Note that although we have given these parameters names for convenience, you do not have to refer to those names in the hook settings. All parameters listed for a particular hook are always passed, whether you want them or not ;-) | 11119 |
| 590 | 8668 | Sample client hook scripts can be found in the |
|
| 591 | 8672 | A small tool is included in the TortoiseSVN installation folder named |
|
| 592 | 8676 | Issue Tracker Integration | 11136 |
| 593 | 8680 | TortoiseSVN can use a COM plugin to query issue trackers when in the commit dialog. The use of such plugins is described in |
11140 |
| 594 | 8688 | 11150 | |
| 595 | 8692 | This property specifies the COM UUID of the IBugtraqProvider, for example |
11154 |
| 596 | 8696 | This is the same as |
|
| 597 | 8700 | This property specifies the parameters passed to the IBugtraqProvider. | 11158 |
| 598 | 8704 | If you want all users to use the same COM plugin for your project, you can specify the plugin also with the properties |
|
| 599 | 8716 | 11178 | |
| 600 | 8720 | Colors | 11182 |
| 601 | 8724 | TortoiseBlame can use the background colour to indicate the age of lines in a file. You set the endpoints by specifying the colours for the newest and oldest revisions, and TortoiseBlame uses a linear interpolation between these colours according to the repository revision indicated for each line. | 11186 |
| 602 | 8732 | You can select the font used to display the text, and the point size to use. This applies both to the file content, and to the author and revision information shown in the left pane. | 11194 |
| 603 | 8736 | Tabs | 11198 |
| 604 | 8740 | Defines how many spaces to use for expansion when a tab character is found in the file content. | 11202 |
| 605 | 8760 | Note that the bug is fixed in VS2005 and later versions. | 11346 |
| 606 | 8772 | Advanced Settings | |
| 607 | 8780 | A few infrequently used settings are available only in the advanced page of the settings dialog. These settings modify the registry directly and you have to know what each of these settings is used for and what it does. Do not modify these settings unless you are sure you need to change them. | |
| 608 | 8784 | You can specify a different location for the Subversion configuration file here. This will affect all TortoiseSVN operations. | |
| 609 | 8788 | Set this to |
|
| 610 | 8792 | To add a cache tray icon for the TSVNCache program, set this value to |
|
| 611 | 8796 | This can be useful if you use something other than the windows explorer or if you get problems with the context menu displaying incorrectly. Set this value to |
|
| 612 | 8800 | If you don't want TortoiseSVN to show icons for the context menus in its own dialogs, set this value to |
|
| 613 | 8804 | The log dialog shows the revision the working copy path is at in bold. But this requires that the log dialog fetches the status of that path. Since for very big working copies this can take a while, you can set this value to |
|
| 614 | 8808 | The status list control which is used in various dialogs (e.g., commit, check-for-modifications, add, revert, ...) uses full row selection (i.e., if you select an entry, the full row is selected, not just the first column). This is fine, but the selected row then also covers the background image on the bottom right, which can look ugly. To disable full row select, set this value to |
|
| 615 | 8812 | The commit and log dialog use styling (e.g. bold, italic) in commit messages (see |
|
| 616 | 8816 | TortoiseSVN uses accelerators for its explorer context menu entries. Since this can lead to doubled accelerators (e.g. the |
|
| 617 | 8820 | As with the explorer, TortoiseSVN shows additional commands if the |
|
| 618 | 8824 | If you don't want the explorer to update the status overlays while another TortoiseSVN command is running (e.g. Update, Commit, ...) then set this value to |
|
| 619 | 8828 | This value contains the URL from which TortoiseSVN tries to download a text file to find out if there are updates available. This might be useful for company admins who don't want their users to update TortoiseSVN until they approve it. | |
| 620 | 8832 | The extra columns the TortoiseSVN adds to the details view in Windows Explorer are normally only active in a working copy. If you want those to be accessible everywhere, not just in working copies, set this value to |
|
| 621 | 8836 | If an update adds a new file from the repository which already exists in the local working copy as an unversioned file, the default action is to keep the local file, showing it as a (possibly) modified version of the new file from the repository. If you would prefer TortoiseSVN to create a conflict in such situations, set this value to |
|
| 622 | 8840 | TortoiseSVN checks whether there's a new version available about once a week. If an updated version is found, the commit dialog shows a link control with that info. If you prefer the old behavior back where a dialog pops up notifying you about the update, set this value to |
|
| 623 | 8844 | TortoiseSVN checks whether there's a new version available about once a week. If you don't want TortoiseSVN to do this check, set this value to |
|
| 624 | 8848 | The auto-completion list shown in the commit message editor displays the names of files listed for commit. To also include these names with extensions removed, set this value to |
|
| 625 | 8852 | When you merge revisions from another branch, and merge tracking information is available, the log messages from the revisions you merge will be collected to make up a commit log message. A pre-defined string is used to separate the individual log messages of the merged revisions. If you prefer, you can set this to a value containing a separator string of your choice. | |
| 626 | 8856 | TortoiseSVN allows you to assign an external diff viewer. Most such viewers, however, are not suited for change blaming ( |
|
| 627 | 8860 | By default, TortoiseSVN always runs an update with externals included. This avoids problems with inconsistent working copies. If you have however a lot of externals set, an update can take quite a while. Set this value to |
|
| 628 | 8864 | In most dialogs in TortoiseSVN, you can use |
|
| 629 | 8868 | Sometimes multiple users use the same account on the same computer. In such situations it's not really wanted to save the authentication data. Setting this value to |
|
| 630 | 9029 | Replaced with the commit date/time of the highest commit revision. By default, international format is used: |
11564 |
| 631 | 9085 | 11635 | |
| 632 | 9093 | 11662 | |
| 633 | 9097 | Replaced with the lock date. Time formatting can be used as described for |
11666 |
| 634 | 9113 | Some of these keywords apply to single files rather than to an entire working copy, so it only makes sense to use these when SubWCRev is called to scan a single file. This applies to |
|
| 635 | 9130 | After running |
11737 |
| 636 | 9139 | A file like this will be included in the build so you would expect it to be versioned. Be sure to version the template file, not the generated file, otherwise each time you regenerate the version file you need to commit the change, which in turn means the version file needs to be updated. | 11777 |
| 637 | 9143 | COM interface | 11781 |
| 638 | 9147 | COM SubWCRev interface | 11785 |
| 639 | 9151 | COM/automation methods supported | 11789 |
| 640 | 9167 | This method traverses the working copy gathering the revision information. Naturally you must call this before you can access the information using the remaining methods. The first parameter is the path. The second parameter should be true if you want to include folder revisions. Equivalent to the |
11809 |
| 641 | 9216 | True if the item is versioned. | 11875 |
| 642 | 9220 | True if the item is locked. | 11885 |
| 643 | 9224 | String representing the date when the lock was created, or an empty string if the item is not locked. | 11889 |
| 644 | 9228 | String representing the lock owner, or an empty string if the item is not locked. | 11893 |
| 645 | 9232 | The message entered when the lock was created. | 11897 |
| 646 | 9236 | If you need to access Subversion revision information from other programs, you can use the COM interface of SubWCRev. The object to create is |
11901 |
| 647 | 9240 | \n // testCOM.js - javascript file\n // test script for the SubWCRev COM/Automation-object\n \n filesystem = new ActiveXObject(\"Scripting.FileSystemObject\");\n \n revObject1 = new ActiveXObject(\"SubWCRev.object\");\n revObject2 = new ActiveXObject(\"SubWCRev.object\");\n revObject3 = new ActiveXObject(\"SubWCRev.object\");\n revObject4 = new ActiveXObject(\"SubWCRev.object\");\n \n revObject1.GetWCInfo(\n filesystem.GetAbsolutePathName(\".\"), 1, 1);\n revObject2.GetWCInfo(\n filesystem.GetAbsolutePathName(\"..\"), 1, 1);\n revObject3.GetWCInfo(\n filesystem.GetAbsolutePathName(\"SubWCRev.cpp\"), 1, 1);\n revObject4.GetWCInfo(\n filesystem.GetAbsolutePathName(\"..\\\\..\"), 1, 1);\n \n wcInfoString1 = \"Revision = \" + revObject1.Revision +\n \"\\n Min Revision = \" + revObject1.MinRev +\n \"\\n Max Revision = \" + revObject1.MaxRev +\n \"\\n Date = \" + revObject1.Date +\n \"\\n URL = \" + revObject1.Url + \"\\n Author = \" +\n revObject1.Author + \"\\n HasMods = \" +\n revObject1.HasModifications + \"\\n IsSvnItem = \" +\n revObject1.IsSvnItem + \"\\n NeedsLocking = \" +\n revObject1.IsLocked + \"\\n LockCreationDate = \" +\n revObject1.LockCreationDate + \"\\n LockOwner = \" +\n revObject1.LockOwner + \"\\n LockComment = \" +\n revObject1.LockComment;\n wcInfoString2 = \"Revision = \" + revObject2.Revision +\n \"\\n Min Revision = \" + revObject2.MinRev +\n \"\\n Max Revision = \" + revObject2.MaxRev +\n \"\\n Date = \" + revObject2.Date +\n \"\\n URL = \" + revObject2.Url + \"\\n Author = \" +\n revObject2.Author + \"\\n HasMods = \" +\n revObject2.HasModifications + \"\\n IsSvnItem = \" +\n revObject2.IsSvnItem + \"\\n NeedsLocking = \" +\n revObject2.IsLocked + \"\\n LockCreationDate = \" +\n revObject2.LockCreationDate + \"\\n LockOwner = \" +\n revObject2.LockOwner + \"\\n LockComment = \" +\n revObject2.LockComment;\n wcInfoString3 = \"Revision = \" + revObject3.Revision +\n \"\\n Min Revision = \" + revObject3.MinRev +\n \"\\n Max Revision = \" + revObject3.MaxRev +\n \"\\n Date = \" + revObject3.Date +\n \"\\n URL = \" + revObject3.Url + \"\\n Author = \" +\n revObject3.Author + \"\\n HasMods = \" +\n revObject3.HasModifications + \"\\n IsSvnItem = \" +\n revObject3.IsSvnItem + \"\\n NeedsLocking = \" +\n revObject3.IsLocked + \"\\n LockCreationDate = \" +\n revObject3.LockCreationDate + \"\\n LockOwner = \" +\n revObject3.LockOwner + \"\\n LockComment = \" +\n revObject3.LockComment;\n wcInfoString4 = \"Revision = \" + revObject4.Revision +\n \"\\n Min Revision = \" + revObject4.MinRev +\n \"\\n Max Revision = \" + revObject4.MaxRev +\n \"\\n Date = \" + revObject4.Date +\n \"\\n URL = \" + revObject4.Url + \"\\n Author = \" +\n revObject4.Author + \"\\n HasMods = \" +\n revObject4.HasModifications + \"\\n IsSvnItem = \" +\n revObject4.IsSvnItem + \"\\n NeedsLocking = \" +\n revObject4.IsLocked + \"\\n LockCreationDate = \" +\n revObject4.LockCreationDate + \"\\n LockOwner = \" +\n revObject4.LockOwner + \"\\n LockComment = \" +\n revObject4.LockComment;\n \n WScript.Echo(wcInfoString1);\n WScript.Echo(wcInfoString2);\n WScript.Echo(wcInfoString3);\n WScript.Echo(wcInfoString4);\n \n |
|
| 648 | 9245 | The following example shows how the interface might be used. |
12036 |
| 649 | 9249 | \n using LibSubWCRev;\n SubWCRev sub = new SubWCRev();\n sub.GetWCInfo(\"C:\\\\PathToMyFile\\\\MyFile.cc\", true, true);\n if (sub.IsSvnItem == true)\n {\n MessageBox.Show(\"versioned\");\n }\n else\n {\n MessageBox.Show(\"not versioned\");\n }\n |
12040 |
| 650 | 9254 | The following listing is an example on how to use the SubWCRev COM object from C#: |
12057 |
| 651 | 9258 | IBugtraqProvider interface | 12061 |
| 652 | 9262 | plugin | 12065 |
| 653 | 9266 | IBugtraqProvider | 12069 |
| 654 | 9270 | To get a tighter integration with issue trackers than by simply using the |
12073 |
| 655 | 9274 | We can't provide information and tutorials on how you have to implement a COM object in your preferred programming language, but we have example plugins in C++/ATL and C# in our repository in the |
12077 |
| 656 | 9278 | You should provide both a 32-bit and 64-bit version of your plugin. Because the x64-Version of TortoiseSVN can not use a 32-bit plugin and vice-versa. | |
| 657 | 9282 | The IBugtraqProvider interface | 12081 |
| 658 | 9286 | TortoiseSVN 1.5 and later can use plugins which implement the IBugtraqProvider interface. The interface provides a few methods which plugins can use to interact with the issue tracker. | |
| 659 | 9290 | \n HRESULT ValidateParameters (\n // Parent window for any UI that needs to be\n // displayed during validation.\n [in] HWND hParentWnd,\n \n // The parameter string that needs to be validated.\n [in] BSTR parameters,\n \n // Is the string valid?\n [out, retval] VARIANT_BOOL *valid\n );\n |
12089 |
| 660 | 9295 | This method is called from the settings dialog where the user can add and configure the plugin. The |
|
| 661 | 9299 | \n HRESULT GetLinkText (\n // Parent window for any (error) UI that needs to be displayed.\n [in] HWND hParentWnd,\n \n // The parameter string, just in case you need to talk to your\n // web service (e.g.) to find out what the correct text is.\n [in] BSTR parameters,\n \n // What text do you want to display?\n // Use the current thread locale.\n [out, retval] BSTR *linkText\n );\n |
12110 |
| 662 | 9304 | The plugin can provide a string here which is used in the TortoiseSVN commit dialog for the button which invokes the plugin, e.g., \"Choose issue\" or \"Select ticket\". Make sure the string is not too long, otherwise it might not fit into the button. If the method returns an error (e.g., |
|
| 663 | 9308 | \n HRESULT GetCommitMessage (\n // Parent window for your provider's UI.\n [in] HWND hParentWnd,\n \n // Parameters for your provider.\n [in] BSTR parameters,\n [in] BSTR commonRoot,\n [in] SAFEARRAY(BSTR) pathList,\n \n // The text already present in the commit message.\n // Your provider should include this text in the new message,\n // where appropriate.\n [in] BSTR originalMessage,\n \n // The new text for the commit message.\n // This replaces the original message.\n [out, retval] BSTR *newMessage\n );\n |
12132 |
| 664 | 9313 | This is the main method of the plugin. This method is called from the TortoiseSVN commit dialog when the user clicks on the plugin button. | |
| 665 | 9317 | The |
|
| 666 | 9321 | The |
|
| 667 | 9325 | The |
|
| 668 | 9329 | The |
|
| 669 | 9333 | The |
|
| 670 | 9337 | The IBugtraqProvider2 interface | 12160 |
| 671 | 9341 | In TortoiseSVN 1.6 a new interface was added which provides more functionality for plugins. This IBugtraqProvider2 interface inherits from IBugtraqProvider. | 12164 |
| 672 | 9345 | \n HRESULT GetCommitMessage2 (\n // Parent window for your provider's UI.\n [in] HWND hParentWnd,\n \n // Parameters for your provider.\n [in] BSTR parameters,\n // The common URL of the commit\n [in] BSTR commonURL,\n [in] BSTR commonRoot,\n [in] SAFEARRAY(BSTR) pathList,\n \n // The text already present in the commit message.\n // Your provider should include this text in the new message,\n // where appropriate.\n [in] BSTR originalMessage,\n \n // You can assign custom revision properties to a commit\n // by setting the next two params.\n // note: Both safearrays must be of the same length.\n // For every property name there must be a property value!\n \n // The content of the bugID field (if shown)\n [in] BSTR bugID,\n \n // Modified content of the bugID field\n [out] BSTR * bugIDOut,\n \n // The list of revision property names.\n [out] SAFEARRAY(BSTR) * revPropNames,\n \n // The list of revision property values.\n [out] SAFEARRAY(BSTR) * revPropValues,\n \n // The new text for the commit message.\n // This replaces the original message\n [out, retval] BSTR * newMessage\n );\n |
12168 |
| 673 | 9350 | This method is called from the TortoiseSVN commit dialog when the user clicks on the plugin button. This method is called instead of |
|
| 674 | 9354 | The parameter |
|
| 675 | 9358 | The parameter |
|
| 676 | 9362 | The return parameter |
|
| 677 | 9366 | The |
|
| 678 | 9370 | \n HRESULT CheckCommit (\n [in] HWND hParentWnd,\n [in] BSTR parameters,\n [in] BSTR commonURL,\n [in] BSTR commonRoot,\n [in] SAFEARRAY(BSTR) pathList,\n [in] BSTR commitMessage,\n [out, retval] BSTR * errorMessage\n );\n |
12215 |
| 679 | 9375 | This method is called right before the commit dialog is closed and the commit begins. A plugin can use this method to validate the selected files/folders for the commit and/or the commit message entered by the user. The parameters are the same as for |
|
| 680 | 9379 | For the branch/tag dialog, the |
|
| 681 | 9383 | The return parameter |
|
| 682 | 9387 | \n HRESULT OnCommitFinished (\n // Parent window for any (error) UI that needs to be displayed.\n [in] HWND hParentWnd,\n \n // The common root of all paths that got committed.\n [in] BSTR commonRoot,\n \n // All the paths that got committed.\n [in] SAFEARRAY(BSTR) pathList,\n \n \n // The text already present in the commit message.\n [in] BSTR logMessage,\n \n // The revision of the commit.\n [in] ULONG revision,\n \n \n // An error to show to the user if this function\n // returns something else than S_OK\n [out, retval] BSTR * error\n );\n |
12234 |
| 683 | 9392 | This method is called after a successful commit. A plugin can use this method to e.g., close the selected issue or add information about the commit to the issue. The parameters are the same as for |
|
| 684 | 9396 | \n HRESULT HasOptions(\n // Whether the provider provides options\n [out, retval] VARIANT_BOOL *ret\n );\n |
12266 |
| 685 | 9401 | This method is called from the settings dialog where the user can configure the plugins. If a plugin provides its own configuration dialog with |
|
| 686 | 9405 | \n HRESULT ShowOptionsDialog(\n // Parent window for the options dialog\n [in] HWND hParentWnd,\n \n // Parameters for your provider.\n [in] BSTR parameters,\n \n // The parameters string\n [out, retval] BSTR * newparameters\n );\n |
12280 |
| 687 | 9410 | This method is called from the settings dialog when the user clicks on the \"Options\" button that is shown if |
|
| 688 | 9414 | The |
|
| 689 | 9418 | The |
|
| 690 | 9426 | FAQ | 12305 |
| 691 | 9438 | ||
| 692 | 9442 | If you want to help out with the development of TortoiseSVN, then you should take part in discussions on |
|
| 693 | 9446 | If you want to help with the translation of the TortoiseSVN user interface or the documentation, send an e-mail to |
|
| 694 | 9450 | If you have a question which is not answered anywhere else, the best place to ask it is on one of the mailing lists: |
|
| 695 | 9470 | reorganize | 12345 |
| 696 | 9691 | Of the three methods described, this is the only one which needs no setup on the client side. Once externals are specified in the folder properties, all clients will get populated folders when they update. | 12642 |
| 697 | 9759 | If the files are already in the repository, they have to be deleted from the repository and added to the ignore list. Fortunately TortoiseSVN has a convenient shortcut for doing this. |
|
| 698 | 9775 | If you have a working copy which you no longer need, how do you get rid of it cleanly? Easy - just delete it in Windows Explorer! Working copies are private local entities, and they are self-contained. | 12798 |
| 699 | 9809 | deploy | 12839 |
| 700 | 9873 | As of version 1.4.0 and later, the TortoiseSVN installer doesn't provide the user with the option to set the |
|
| 701 | 9893 | As of version 1.5.0 and later, TortoiseSVN allows you to disable (actually, hide) context menu entries. Since this is a feature which should not be used lightly but only if there is a compelling reason, there is no GUI for this and it has to be done directly in the registry. This can be used to disable certain commands for users who should not use them. But please note that only the context menu entries in the |
12967 |
| 702 | 9897 | The registry keys which hold the information on which context menus to show are |
12971 |
| 703 | 9901 | Each of these registry entries is a |
12975 |
| 704 | 9905 | Menu entries and their values | 12979 |
| 705 | 9913 | Menu entry | 12988 |
| 706 | 10055 | Diff with URL | 13158 |
| 707 | 10067 | Help | 13173 |
| 708 | 10071 | About | 13177 |
| 709 | 10075 | Example: to disable the Relocatethe Delete unversioned itemsand the Settingsmenu entries, add the values assigned to the entries like this: 0x0000000000080000\n + 0x0000000080000000\n + 0x2000000000000000\n = 0x2000000080080000\n |
13181 |
| 710 | 10079 | To enable the menu entries again, simply delete the two registry keys. | 13191 |
| 711 | 10123 | You can also specify a file which contains a list of paths, separated by newlines. The file must be in UTF-16 format. If you pass such a file, use instead of . To have TortoiseProc delete that file after the command is finished, you can pass the parameter . | 13244 |
| 712 | 10222 | /findstring:\"filterstring\" | 13362 |
| 713 | 10226 | /findtext | 13366 |
| 714 | 10230 | /findregex | 13370 |
| 715 | 10234 | /findtype:X | 13374 |
| 716 | 10238 | filter by everything | 13378 |
| 717 | 10242 | filter by messages | 13382 |
| 718 | 10246 | filter by path | 13386 |
| 719 | 10250 | filter by authors | 13390 |
| 720 | 10254 | filter by revisions | 13394 |
| 721 | 10258 | filter by bug ID | 13398 |
| 722 | 10295 | /includeexternals | |
| 723 | 10299 | Updates the working copy in |
|
| 724 | 10309 | /logmsgfile:path | 13456 |
| 725 | 10338 | Cleans up interrupted or aborted operations and unlocks the working copy in |
13493 |
| 726 | 10427 | Depending on the URLs and revisions to compare, this either shows a unified diff (if the option is set), a dialog with a list of files that have changed or if the URLs point to files starts the diff viewer for those two files. | 13607 |
| 727 | 10431 | The options , , and must be specified. The options , , and are optional. | 13611 |
| 728 | 10480 | Opens the blame dialog for the file specified in . | 13677 |
| 729 | 10484 | If the options and are set, then the dialog asking for the blame range is not shown but the revision values of those options are used instead. | 13681 |
| 730 | 10488 | If the option is set, TortoiseBlame will open with the specified line number showing. | 13685 |
| 731 | 10492 | The options , and are also supported. | 13689 |
| 732 | 10536 | Tsvncmd URL handler | 13765 |
| 733 | 10544 | Using special URLs, it is also possible to call TortoiseProc from a web page. | 13775 |
| 734 | 10548 | TortoiseSVN registers a new protocol |
13779 |
| 735 | 10552 | The format of the |
13783 |
| 736 | 10556 | tsvncmd:command:cmd?parameter:paramvalue?parameter:paramvalue | 13787 |
| 737 | 10560 | with |
13791 |
| 738 | 10568 | \n <a href=\"tsvncmd:command:showcompare?\n url1:https://stexbar.googlecode.com/svn/trunk/StExBar/src/setup/Setup.wxs?\n url2:https://stexbar.googlecode.com/svn/trunk/StExBar/src/setup/Setup.wxs?\n revision1:188?revision2:189\">compare</a>\n |
13801 |
| 739 | 10573 | An example URL might look like this: |
13811 |
| 740 | 10581 | The image diff tool has a few command line options which you can use to control how the tool is started. The program is called |
13820 |
| 741 | 10585 | The table below lists all the options which can be passed to the image diff tool on the command line. | 13824 |
| 742 | 10593 | Option | 13833 |
| 743 | 10597 | Path to the file shown on the left. | 13837 |
| 744 | 10602 | A title string. This string is used in the image view title instead of the full path to the image file. | 13842 |
| 745 | 10606 | Path to the file shown on the right. | 13846 |
| 746 | 10610 | If specified, the image diff tool switches to the overlay mode (alpha blend). | 13850 |
| 747 | 10614 | If specified, the image diff tool fits both images together. | 13854 |
| 748 | 10618 | Shows the image info box. | 13858 |
| 749 | 10622 | Example (which should be entered on one line): TortoiseIDiff.exe /left:\"c:\\images\\img1.jpg\" /lefttitle:\"image 1\"\n /right:\"c:\\images\\img2.jpg\" /righttitle:\"image 2\"\n /fit /overlay\n |
13862 |
| 750 | 10654 | In the descriptions which follow, the URL for a repository location is shown simply as |
|
| 751 | 10666 | \n svn checkout [-depth ARG] [--ignore-externals] [-r rev] URL PATH\n |
|
| 752 | 10672 | The depth combo box items relate to the |
|
| 753 | 10706 | \n svn info URL_of_WC\n svn update [-r rev] [-depth ARG] [--ignore-externals] PATH\n |
|
| 754 | 10741 | \n svn commit -m \"LogMessage\" [-depth ARG] [--no-unlock] PATH...\n |
|
| 755 | 11006 | Implementation Details | 14500 |
| 756 | 11014 | overlay priority | 14510 |
| 757 | 11018 | Every file and folder has a Subversion status value as reported by the Subversion library. In the command line client, these are represented by single letter codes, but in TortoiseSVN they are shown graphically using the icon overlays. Because the number of overlays is very limited, each overlay may represent one of several status values. | 14514 |
| 758 | 11022 | 14518 | |
| 759 | 11026 | 14522 | |
| 760 | 11030 | 14526 | |
| 761 | 11038 | 14536 | |
| 762 | 11042 | 14540 | |
| 763 | 11046 | 14544 | |
| 764 | 11050 | 14548 | |
| 765 | 11054 | 14552 | |
| 766 | 11058 | If an item has subversion status |
14556 |
| 767 | 11062 | An item can only have one Subversion status value. For example a file could be locally modified and it could be marked for deletion at the same time. Subversion returns a single status value - in this case |
14560 |
| 768 | 11066 | When TortoiseSVN displays the status recursively (the default setting), each folder displays an overlay reflecting its own status and the status of all its children. In order to display a single |
14564 |
| 769 | 11098 | This section provides a step-by-step guide to setting up Subversion and TortoiseSVN to use the |
14609 |
| 770 | 11102 | In this implementation we create a single SSH user account for all subversion users, and use different authentication keys to differentiate between the real Subversion users. | 14613 |
| 771 | 11106 | In this appendix we assume that you already have the subversion tools installed, and that you have created a repository as detailed elsewhere in this manual. Note that you should |
14617 |
| 772 | 11110 | Much of the information here comes from a tutorial provided by Marc Logemann, which has been archived at |
|
| 773 | 11114 | You can also watch a video tutorial created by Maximo Migliari which takes you through all the important steps. Watch it on |
14625 |
| 774 | 11122 | You need to have SSH enabled on the server, and here we assume that you will be using OpenSSH. On most distributions this will already be installed. To find out, type: ps xa | grep sshd\n |
14634 |
| 775 | 11126 | One point to note is that if you build Subversion from source and do not provide any argument to |
14641 |
| 776 | 11130 | To check that everything is OK, login in as the target user with SSH and type: which svnserve\n |
14645 |
| 777 | 11134 | Create a new user which we will use to access the svn repository: useradd -m svnuser\n |
14652 |
| 778 | 11142 | Install Cygwin SSH daemon as described here: |
14664 |
| 779 | 11146 | Create a new Windows user account |
14668 |
| 780 | 11150 | If there is no password file yet then create one from the Cygwin console using: mkpasswd -l > /etc/passwd\n |
14672 |
| 781 | 11158 | Grab the tools we need for using SSH on the windows client from this site: |
14684 |
| 782 | 11162 | Creating OpenSSH Certificates | 14688 |
| 783 | 11166 | The next step is to create a key pair for authentication. There are two possible ways to create keys. The first is to create the keys with PuTTYgen on the client, upload the public key to your server and use the private key with PuTTY. The other is to create the key pair with the OpenSSH tool ssh-keygen, download the private key to your client and convert the private key to a PuTTY-style private key. | 14692 |
| 784 | 11170 | Create Keys using ssh-keygen | 14696 |
| 785 | 11174 | Login to the server as ssh-keygen -b 1024 -t dsa -N passphrase -f keyfile\n ls -l keyfile*\n |
14700 |
| 786 | 11178 | Append the public key to those in the cat keyfile.pub >> /home/svnuser/.ssh/authorized_keys\n |
14709 |
| 787 | 11182 | In order to use the private key we generated, we have to convert it to a putty format. This is because the private key file format is not specified by a standards body. After you download the private key file to your client PC, start PuTTYgen and use |
14716 |
| 788 | 11186 | Create Keys using PuTTYgen | 14720 |
| 789 | 11190 | Use PuTTYgen to generate a public-key/private-key pair and save it. Copy the public key to the server and append it to those in the cat keyfile.pub >> /home/svnuser/.ssh/authorized_keys\n |
14724 |
| 790 | 11194 | Test using PuTTY | 14731 |
| 791 | 11198 | To test the connection we will use PuTTY. Start the program and on the |
14735 |
| 792 | 11202 | Click on |
14739 |
| 793 | 11206 | You may need to edit PubkeyAuthentication yes\n PasswordAuthentication no\n PermitEmptyPasswords no\n ChallengeResponseAuthentication no\n |
14743 |
| 794 | 11214 | So far we have only tested that you can login using SSH. Now we need to make sure that the SSH connection can actually run svnserve. On the server modify |
14758 |
| 795 | 11218 | Note: This is all on one very long line. command=\"svnserve -t -r <ReposRootPath> --tunnel-user=<author>\",\n no-port-forwarding,no-agent-forwarding,no-X11-forwarding,\n no-pty ssh-rsa <PublicKey> <Comment>\n |
14762 |
| 796 | 11222 | 14771 | |
| 797 | 11226 | 14775 | |
| 798 | 11230 | 14779 | |
| 799 | 11234 | 14783 | |
| 800 | 11238 | Right click on any folder in Windows Explorer and select svn+ssh://svnuser@SvnConnection/repos\n |
14787 |
| 801 | 11242 | Click on |
14794 |
| 802 | 11246 | Note that by default TortoiseSVN uses its own version of Plink to connect. This avoids a console window popping up for every authentication attempt, but it also means that there is nowhere for error messages to appear. If you receive the error Unable to write to standard output, you can try specifying Plink as the client in TortoiseSVN's network settings. This will allow you to see the real error message generated by Plink. |
14798 |
| 803 | 11254 | One way to simplify the URL in TortoiseSVN is to set the user inside the PuTTY session. For this you have to load your already defined session svn+ssh://SvnConnection/repos\n |
14808 |
| 804 | 11258 | At the time of writing PuTTY does not check all saved configurations, so if you have multiple configurations with the same server name, it will pick the first one which matches. Also, if you edit the default configuration and save it, the auto login user name is |
14815 |
| 805 | 11262 | Many people like to use Pageant for storing all their keys. Because a PuTTY session is capable of storing a key, you don't always need Pageant. But imagine you want to store keys for several different servers; in that case you would have to edit the PuTTY session over and over again, depending on the server you are trying to connect with. In this situation Pageant makes perfect sense, because when PuTTY, Plink, TortoisePlink or any other PuTTY-based tool is trying to connect to an SSH server, it checks all private keys that Pageant holds to initiate the connection. | 14819 |
| 806 | 11266 | For this task, simply run Pageant and add the private key. It should be the same private key you defined in the PuTTY session above. If you use Pageant for private key storage, you can delete the reference to the private key file in your saved PuTTY session. You can add more keys for other servers, or other users of course. | 14823 |
| 807 | 11270 | If you don't want to repeat this procedure after every reboot of your client, you should place Pageant in the auto-start group of your Windows installation. You can append the keys with complete paths as command line arguments to Pageant.exe | 14827 |
| 808 | 11274 | The last way to connect to an SSH server is simply by using this URL inside TortoiseSVN: svn+ssh://svnuser@100.101.102.103/repos\n svn+ssh://svnuser@mydomain.com/repos\n |
14831 |
| 809 | 11278 | If you use this last method, be sure you do not have a default username set in PuTTY. We have had reports of a bug in PuTTY causing connections to close in this case. To remove the default user, simply clear |
14839 |
| 810 | 11282 | Language Packs and Spell Checkers | |
| 811 | 11286 | The standard installer has support only for English, but you can download separate language packs and spell check dictionaries separately after installation. | |
| 812 | 11302 | The TortoiseSVN user interface has been translated into many different languages, so you may be able to download a language pack to suit your needs. You can find the language packs on our |
|
| 813 | 11306 | Each language pack is packaged as a |
|
| 814 | 11310 | The documentation has also been translated into several different languages. You can download translated manuals from the |
|
| 815 | 11330 | The installer automatically adds the US and UK English dictionaries. If you want other languages, the easiest option is simply to install one of TortoiseSVN's language packs. This will install the appropriate dictionary files as well as the TortoiseSVN local user interface. After the installation finishes, the dictionary will be available too. |
Total:815
String marked as fuzzy is not in final shape.
| Index | Line | English | Line | Native |
| 1 | - | The chapter on |
138 | Bab |
| 2 | - | The section on |
159 | Seksi |
| 3 | - | The |
165 | |
| 4 | - | TortoiseSVN is an Open Source project. That means you have full read access to the source code of this program. You can browse it on this link |
181 | TortoiseSVN adalah proyek Sumber Terbuka. Itu berarti Anda mempunyai akses penuh ke kode sumber dari program ini. Anda bisa melihatnya pada link ini |
| 5 | - | Both TortoiseSVN and Subversion are developed by a community of people who are working on those projects. They come from different countries all over the world and work together to create wonderful programs. | 192 | TortoiseSVN dan Subversion dikembangkan oleh komunitas orang yang bekerja pada proyek itu. Mereka datang dari berbagai negara di seluruh dunia dan bergabung bersama untuk membuat program yang baik. |
| 6 | - | for the beautiful icons, logo, bug hunting, translating and managing the translations | 228 | untuk ikon yang indah, logo, pemburuan bug dan memelihara dokumentasi |
| 7 | - | User Actions are indicated using a bold font. |
307 | Aksi Pengguna ditunjukan menggunakan font tebal. |
| 8 | - | Tim studied the source code of TortoiseCVS and used it as a base for TortoiseSVN. He then started the project, registered the domain |
380 | Tim mempelajari kode sumber TortoiseCVS dan menggunakannya sebagai dasar untuk TortoiseSVN. Kemudian dia memulai proyek, domain teregistrasi tortoisesvn.org dan menyimpan kode sumber secara online. Selama waktu itu, Stefan Küng sedang mencari sistem kontrol versi yang baik dan bebas dan menemukan Subversion serta sumber untuk TortoiseSVN. Karena TortoiseSVN masih belum siap untuk digunakan maka dia bergabung dengan proyek dan memulai pemrograman. Segera setelah dia menulis ulang banyak dari kode yang sudah ada dan mulai menambahkan perintah serta fitur, sampai ke titik di mana tidak ada kode asli yang tersisa. |
| 9 | - | As Subversion became more stable it attracted more and more users who also started using TortoiseSVN as their Subversion client. The user base grew quickly (and is still growing every day). That's when Lübbe Onken offered to help out with some nice icons and a logo for TortoiseSVN. And he takes care of the website and manages the translation. | 386 | Karena Subversion menjadi lebih stabil ia menarik semakin banyak pengguna yang juga mulai menggunakan TortoiseSVN sebagai klien Subversion-nya. Basis pengguna tumbuh dengan cepat (dan masih tumbuh setiap hari). Itulah ketika Lübbe Onken menawarkan membantu dengan beberapa ikon bagus dan logo untuk TortoiseSVN. Dan dia memelihara situs serta mengatur terjemahan. |
| 10 | - | TortoiseSVN runs on Windows 2000 SP2, Windows XP or higher. Windows 98, Windows ME and Windows NT4 are no longer supported since TortoiseSVN 1.2.0, but you can still download the older versions if you really need them. | 532 | TortoiseSVN berjalan pada Win2k SP2, WinXP atau lebih tinggi. Windows 98, Windows ME dan Windows NT4 tidak lagi didukung sejak TortoiseSVN 1.2.0, tapi Anda masih bisa mengunduh versi lebih lama jika Anda benar-benar membutuhkannya. |
| 11 | - | The installer automatically adds the US and UK English dictionaries. If you want other languages, the easiest option is simply to install one of TortoiseSVN's language packs. This will install the appropriate dictionary files as well as the TortoiseSVN local user interface. Next time you restart, the dictionary will be available too. | 606 | Instalator secara otomatis menambahkan kamus bahasa ingris US dan UK. Jika Anda ingin bahasa lain, opsi termudah cukup instalasi salah satu dari paket bahasa TortoiseSVN. Ini akan menginstalasi file kamus yang benar juga interface pengguna lokal TortoiseSVN. Lain kali Anda memulai, kamus akan tersedia juga. |
| 12 | - | Or you can install the dictionaries yourself. If you have OpenOffice or Mozilla installed, you can copy those dictionaries, which are located in the installation folders for those applications. Otherwise, you need to download the required dictionary files from |
612 | Atau Anda bisa menginstalasi kamus oleh Anda sendiri. Jika Anda mempunyai OpenOffice atau Mozilla terinstalasi, Anda bisa menyalin kamus itu, yang ditempatkan dalam folder instalasi untuk aplikasi itu. Sebaliknya, Anda perlu mendownload file kamus yang dibutuhkan dari |
| 13 | - | If none of the above works, then the default language is English, which is included with the standard installation. | 648 | Jika tidak satupun di atas yang bekerja, maka bahasa standar adalah bahasa Inggris, yang disertakan dengan instalasi standar. |
| 14 | - | Basic Version-Control Concepts | 659 | Konsep Dasar |
| 15 | - | When a client reads data from the repository, it normally sees only the latest version of the filesystem tree. But the client also has the ability to view what did this directory contain last Wednesday?, or who was the last person to change this file, and what changes did they make?These are the sorts of questions that are at the heart of any |
713 | Ketika klien membaca data dari repositori, ia biasanya hanya melihat versi terbaru dari susunan sistem file. Tapi klien juga mempunyai kemampuan untuk melihat keadaan sistem file |
| 16 | - | Many version control systems use a |
750 | Banyak sistem kontrol versi menggunakan model |
| 17 | - | Here's an example. Say that Harry and Sally each create working copies of the same project, copied from the repository. They work concurrently, and make changes to the same file |
787 | Ini adalah sebuah contoh. Katakanlah bahwa Harry dan Sally masing-masing membuat copy pekerjaan dari proyek yang sama, disalin dari repositori. Mereka bekerja secara konkuren, dan membuat perubahan pada file \"A\" yang sama dalam salinan mereka. Sally menyimpan perubahannya ke repositori terlebih dahulu. Ketika Harry mencoba untuk menyimpan perubahannya nanti, repositori menginformasikan bahwa filenya |
| 18 | - | There is one common situation where the lock-modify-unlock model comes out better, and that is where you have unmergeable files. For example if your repository contains some graphic images, and two people change the image at the same time, there is no way for those changes to be merged together. Either Harry or Sally will lose their changes. | 819 | Ada satu situasi umum di mana model kunci-ubah-buka kunci jauh lebih baik, dan itu adalah di mana Anda sudah tidak menggabung file. Sebagai contoh jika repositori Anda berisi beberapa gambar grafik, dan dua orang mengubah gambar pada saat yang sama, tidak ada cara untuk kedua perubahan itu untuk digabung bersama. Salah satu dari Harry atau Sally akan kehilangan perubahannya. |
| 19 | - | After you've made some changes to the files in your working copy and verified that they work properly, Subversion provides you with commands to |
860 | Setelah Anda membuat beberapa perubahan pada file dalam copy pekerjaan Anda dan memverifikasi bahwa mereka bekerja dengan benar, Subversion menyediakan kepada Anda perintah untuk \"menerbitkan\" perubahan Anda ke orang lain yang bekerja dengan Anda pada proyek Anda (dengan menulis ke repositori). Jika orang lain menerbitkan perubahan mereka sendiri, Subversion menyediakan kepada Anda perintah untuk menggabung perubahan-perubahan itu ke dalam direktori pekerjaan Anda (dengan membacanya dari repositori). |
| 20 | - | To get a working copy, you must |
891 | Untuk mendapatkan copy pekerjaan, Anda harus melakukan |
| 21 | - | Unauthenticated TCP/IP access via custom protocol to a |
996 | Akses TCP/IP tidak terotentikasi via protokol kustom ke suatu server |
| 22 | - | authenticated, encrypted TCP/IP access via custom protocol to a |
1007 | terotentikasi, akses TCP/IP terenkripsi via protokol bebas ke suatu server |
| 23 | - | For the most part, Subversion's URLs use the standard syntax, allowing for server names and port numbers to be specified as part of the URL. The |
1013 | Untuk bagian terbanyak, URL Subversion menggunakan sintaks standar, membolehkan nama server dan nomor port ditetapkan sebagai bagian dari URL. Metode akses |
| 24 | - | Also, users of the standardsyntax for accessing repositories that are on the same machine, but on a different drive than the client's current working drive. Either of the two following URL path syntaxes will work where |
1019 | Juga, para pengguna skema standaruntuk pengaksesan repositori yang ada pada mesin yang sama, tapi pada drive yang berbeda dari drive klien pekerjaan saat ini. Baik dua sintaks path URL berikut akan bekerja di mana |
| 25 | - | You can safely access a FSFS repository via a network share, but you |
1046 | Anda bisa mengakses repositori FSFS dengan aman via jaringan berbagi, tapi Anda |
| 26 | - | A |
1069 | Operasi |
| 27 | - | In the repository, each commit is treated as an atomic transaction: either all the commits changes take place, or none of them take place. Subversion retains this atomicity in the face of program crashes, system crashes, network problems, and other users' actions. | 1075 | Dalam repositori, setiap komit diperlakukan sebagai transaksi atomis: baik semua perubahan komit dimulai, ataupun tidak ada yang dimulai. Subversion mencoba untuk mempertahankan atomisitis ini saat menghadapi kerusakan program, kerusakan sistem, masalah jaringan, dan tindakan pengguna lainnya. |
| 28 | - | The file has been changed in the working directory, and no changes to that file have been committed to the repository since its base revision. There are local changes that have not been committed to the repository, thus a |
1203 | File sudah diubah dalam direktori pekerjaan, dan tidak ada perubahan ke file itu yang telah dikomit ke repositori sejak revisi base-nya. Ada perubahan lokal yang belum dikomit ke repositori sehingga |
| 29 | - | The file has not been changed in the working directory, but it has been changed in the repository. The file should eventually be updated, to make it current with the public revision. A |
1214 | File belum diubah dalam direktori pekerjaan, tapi sudah diubah dalam repositori. Alhasil file harus dimutahirkan untuk membuatnya saat ini dengan revisi umum. |
| 30 | - | The file has been changed both in the working directory, and in the repository. A |
1225 | File telah diubah dalam copy pekerjaan dan dalam repositori. |
| 31 | - | create repository | 1271 | Buat Repositori Disini |
| 32 | - | You can create a repository with the FSFS backend or with the older Berkeley Database (BDB) format. The FSFS format is generally faster and easier to administer, and it works on network shares and Windows 98 without problems. The BDB format was once considered more stable simply because it has been in use for longer, but since FSFS has now been in use in the field for several years, that argument is now rather weak. Read |
1277 | Anda bisa membuat repositori dengan ujung belakang FSFS atau dengan format lama tapi stabil Berkeley Database (BDB). Format FSFS lebih cepat dan sekarang bekerja pada jaringan berbagi dan Windows 98 tanpa masalah. Format BDB lebih stabil karena sudah diuji lebih lama. Baca |
| 33 | - | Do not create or access a Berkeley DB repository on a network share. It |
1401 | Jangan membuat atau mengakses repositori Berkeley DB pada jaringan berbagi. Ia |
| 34 | - | There are some standard, recommended ways to organize a repository. Most people create a main lineof development, a |
1446 | Ada beberapa standar, cara yang direkomendasikan untuk mengatur repositori. Banyak orang membuat direktori |
| 35 | - | Server side hook scripts | 1617 | Naskah Hook |
| 36 | - | server side hook scripts | 1634 | Naskah Hook |
| 37 | - | A hook script is a program triggered by some repository event, such as the creation of a new revision or the modification of an unversioned property. Each hook is handed enough information to tell what that event is, what target(s) it's operating on, and the username of the person who triggered the event. Depending on the hook's output or return status, the hook program may continue the action, stop it, or suspend it in some way. Please refer to the chapter on |
1640 | Naskah hook adalah program yang dipicu oleh beberapa peristiwa repositori, seperti pembuatan revisi baru atau modifikasi dari properti tidak berversi. Setiap hook diberi informasi cukup untuk memberitahu apa peristiwa itu, apa sasaran operasinya, dan nama pengguna dari orang yang memicu peristiwa. Tergantung pada output hook atau status hasil, program hook bisa melanjutkan tindakan, atau menghentikannya, atau menundanya dalam beberapa cara. Silahkan rujuk ke bab pada |
| 38 | - | TortoiseSVN link | 1685 | TortoiseSVN |
| 39 | - | If you want to make your Subversion repository available to others you may want to include a link to it from your website. One way to make this more accessible is to include a |
1699 | Jika Anda ingin membuat repositori Subversion Anda tersedia bagi yang lain Anda mungkin ingin menyertakan link dari website Anda. Satu cara untuk membuat ini lebih bisa diakses adalah menyertakan |
| 40 | - | When you install TortoiseSVN, it registers a new |
1705 | Ketika Anda menginstalasi TortoiseSVN, ia meregister protokol |
| 41 | - | Of course it would look even better if you included a suitable picture. You can use the |
1738 | Tentu saja ini akan terlihat bahkan lebih baik jika Anda menyertakan gambar yang cukup. Anda bisa menggunakan |
| 42 | - | To use TortoiseSVN (or any other Subversion client), you need a place where your repositories are located. You can either store your repositories locally and access them using the |
1764 | Untuk menggunakan TortoiseSVN (atau klien Subversion lain), Anda memerlukan tempat di mana repositori Anda ditempatkan. Anda bisa menyimpan repositori Anda secara lokal dan mengaksesnya menggunakan protokol |
| 43 | - | If you don't have a server and you work alone, or if you are just evaluating Subversion and TortoiseSVN in isolation, then local repositories are probably your best choice. Just create a repository on your own PC as described earlier in |
1774 | Jika Anda tidak mempunyai server dan/atau jika Anda hanya bekerja sendiri maka repositori lokal mungkin pilihan terbaik Anda. Anda bisa melewatkan bab ini dan langsung pergi ke |
| 44 | - | The next sections are a step-by-step guide on how you can set up such a server on a Windows machine. Of course you can also set up a server on a Linux machine, but that is beyond the scope of this guide. More detailed information on the Subversion server options, and how to choose the best architecture for your situation, can be found in the Subversion book under |
1784 | Satu-satunya cara untuk menghapus data dari repositori adalah menggunakan piranti baris perintah Subversion |
| 45 | - | In most cases svnserve is easier to setup and runs faster than the Apache based server, although it doesn't have some of the advanced features. And now that SASL support is included it is easy to secure as well. | 1799 | Dalam banyak kasus svnserve lebih mudah disiapkan dan berjalan lebih cepat daripada server berbasis Apache. |
| 46 | - | Run the Subversion installer. If you run the installer on your server (recommended) you can skip step 4. | 1819 | Jalankan instalator Subversion. Jika Anda menjalankan instalator pada server Anda bisa melewati langkah ke-4. |
| 47 | - | You can also increase security and save time entering URLs with svnserve by using the --root switch to set the root location and restrict access to a specified directory on the server: svnserve.exe --daemon --root drive:\\path\\to\\repository\\root\n svnserve.exe --daemon --root c:\\repos\n svn://localhost/TestRepo\n |
1867 | Anda juga bisa meningkatkan keamanan dan menghemat waktu memasukan Url dengan svnserve dengan menggunakan saklar --root untuk men-set akar lokasi dan membatasi akses ke direktori tertentu pada server: svnserve.exe --daemon --root drive:\\path\\to\\repository\\root\n svnserve.exe --daemon --root c:\\repos\n svn://localhost/TestRepo\n |
| 48 | - | Microsoft now recommend services to be run as under either the Local Service or Network Service account. Refer to obj= \"NT AUTHORITY\\LocalService\"\n |
1932 | Microsoft sekarang merekomendasikan layanan dijalankan dibawah baik akun Local Service atau Network Service. Lihat obj= \"NT AUTHORITY\\LocalService\"\n |
| 49 | - | If you installed an earlier version of svnserve using the svnservice -remove\n |
1951 | Jika Anda memasang versi svnserve yang lebih awal dengan menggunakan pembungkus svnservice -remove\n |
| 50 | - | The default svnserve setup provides anonymous read-only access. This means that you can use an |
1968 | Penyiapan standar svnserve menyediakan akses hanya-baca anonim. Ini berarti bahwa Anda bisa menggunakan URL |
| 51 | - | One way to overcome this is to create a password database: [general]\n anon-access = none\n auth-access = write\n password-db = userfile\n [users]\n username = password\n ...\n |
1992 | Satu cara untuk mengatasi ini adalah membuat database kata sandi: [general]\n anon-access = none\n auth-access = write\n password-db = userfile\n [users]\n username = password\n ...\n |
| 52 | - | If you maintain multiple repositories using the same password database, the use of an authentication realm will make life easier for users, as TortoiseSVN can cache your credentials so that you only have to enter them once. More information can be found in the Subversion book, specifically in the sections |
2018 | Jika Anda memelihara multipel repositori menggunakan database kata sandi sama, kegunaan otentikasi akan membuatnya lebih mudah bagi pengguna, karena TortoiseSVN bisa menyimpan mandat Anda agar Anda hanya perlu memasukannya sekali. Informasi lebih jauh bisa ditemukan dalam buku Subversion, terutama dalam seksi < |
| 53 | - | Another way to authenticate users with a svnserve based server is to use a secure shell (SSH) to tunnel requests through. It is not as simple to set up as SASL, but it may be useful is some cases. | 2115 | Cara lain untuk mengotentikasi pengguna dengan server berbasis svnserve adalah dengan menggunakan secure shell (SSH) untuk menjembatani permintaan. |
| 54 | - | The Apache based Subversion server uses the WebDAV protocol which is supported by many other programs as well. You could e.g. mount such a repository as a Web folderin the Windows explorer and then access it like any other folder in the file system. |
2174 | Server Subversion berbasis Apache menggunakan protokol WebDAV yang didukung oleh banyak program lain juga. Anda bisa contohmya menghidupkan repositori itu sebagai \"Webfolder\" dalam Windows explorer dan kemudian mengaksesnya seperti folder lain dalam sistem file |
| 55 | - | Please note that Windows XP without the service pack 1 will lead to bogus network data and could therefore corrupt your repository! | 2216 | Harap dicatat bahwa Windows XP tanpa servicepack 1 akan membawa data jaringan aneh dan akibatnya bisa merusak repositori Anda! |
| 56 | - | Once you have the Apache2 installer you can double click on it and it will guide you through the installation process. Make sure that you enter the server-URL correctly (if you don't have a DNS name for your server just enter the IP-address). I recommend to install Apache |
2231 | Sekali Anda mempunyai instalator Apache2 Anda bisa mengklik ganda dan ia akan membimbing Anda melalui proses instalasi. Pastikan bahwa Anda memasukkan URL-server dengan benar (jika Anda tidak mempunyai nama dns untuk server Anda, cukup masukan alamat ip). Saya merekomendasikan untuk menginstalasi Apache |
| 57 | - | Now test if the Apache web server is running correctly by pointing your web browser to |
2237 | Sekarang uji apakah Apache-webserver berjalan dengan benar dengan mengarahkan webbrowser Anda ke |
| 58 | - | If Apache does not have this permission set up, your users will get Access deniederror messages, which show up in the Apache error log as error 500. |
2258 | Jika Apache tidak mempunyai perijinan ini disiapkan, pengguna Anda akan mendapatkan pesan kesalahan \"Access denied\", yang muncul dalam log kesalahan Apache sebagai kesalahan 500. |
| 59 | - | The first thing you need before installing Apache is a computer with Windows 2000, Windows XP+SP1, Windows 2003, Vista or Server 2008. |
2264 | Hal pertama yang Anda perlukan sebelum menginstalasi Apache adalah komputer dengan Windows2000 / WinXP+SP1 atau Windows2003. |
| 60 | - | Download the latest version of the Subversion Win32 binaries for Apache. Be sure to get the right version to integrate with your version of Apache, otherwise you will get an obscure error message when you try to restart. If you have Apache 2.2.x go to |
2275 | Download versi terbaru Subversion dari |
| 61 | - | Uncomment (remove the ' #LoadModule dav_fs_module modules/mod_dav_fs.so\n #LoadModule dav_module modules/mod_dav.so\n LoadModule dav_svn_module modules/mod_dav_svn.so\n LoadModule authz_svn_module modules/mod_authz_svn.so\n |
2307 | Hapus komentar (hapus tanda ' LoadModule dav_svn_module modules/mod_dav_svn.so\n LoadModule authz_svn_module modules/mod_authz_svn.so\n |
| 62 | - | At the end of the config file add the following lines: <Location /svn>\n DAV svn\n SVNListParentPath on\n SVNParentPath D:\\SVN\n #SVNIndexXSLT \"/svnindex.xsl\"\n AuthType Basic\n AuthName \"Subversion repositories\"\n AuthUserFile passwd\n #AuthzSVNAccessFile svnaccessfile\n Require valid-user\n </Location>\n |
2330 | Di akhir file Konfig tambah baris berikut: <Location /svn>\n DAV svn\n SVNListParentPath on\n SVNParentPath D:\\SVN\n #SVNIndexXSLT \"/svnindex.xsl\"\n AuthType Basic\n AuthName \"Subversion repositories\"\n AuthUserFile passwd\n #AuthzSVNAccessFile svnaccessfile\n Require valid-user\n </Location>\n |
| 63 | - | To create the bin\\htpasswd -c passwd <username>\n bin\\htpasswd passwd <username>\n |
2362 | Untuk membuat file bin\\htpasswd -c passwd <username>\n bin\\htpasswd passwd <username>\n |
| 64 | - | Now you have set up Apache and Subversion, but Apache doesn't know how to handle Subversion clients like TortoiseSVN yet. To get Apache to know which URL will be used for Subversion repositories you have to edit the Apache configuration file (usually located in |
2388 | Sekarang Anda telah menyiapkan Apache dan Subversion, tapi Apache tidak mengetahui bagaimana menangani klien-klien Subversion. Untuk membuat Apache mengetahui URL yang mana yang harus digunakan untuk repositori Subversion, Anda perlu mengedit file konfig Apache (biasanya ditempatkan di |
| 65 | - | Apache |
2406 | Seting httpd.conf Apache |
| 66 | - | For Subversion version 1.3 and higher, this directive enables listing all the available repositories under |
2437 | Untuk versi Subversion 1.3 dan lebih tinggi, direktif ini menghidupkan pendaftaran semua repositori yang tersedia dibawah SVNParentPath. |
| 67 | - | Used to make the browsing with a web browser prettier. | 2452 | Digunakan untuk membuat penjelajahan dengan penjelajah jaringan lebih cantik. |
| 68 | - | Using a #AuthzSVNAccessFile svnaccessfile\n |
2502 | Menggunakan batas file #AuthzSVNAccessFile svnaccessfile\n |
| 69 | - | To make browsing the repository with a web browser 'prettier', uncomment the line #SVNIndexXSLT \"/svnindex.xsl\"\n |
2513 | Untuk membuat penjelajahan repositori dengan suatu penjelajah web lebih 'cantik', batalkan komentar pada baris #SVNIndexXSLT \"/svnindex.xsl\"\n |
| 70 | - | You can get those three files directly from our source repository at |
2524 | Anda dapat mendapatkan ketiga file tersebut langsung dari repositori sumber kami di |
| 71 | - | The XSL file from the TortoiseSVN repository has a nice gimmick: if you browse the repository with your web browser, then every folder in your repository has an icon on the right shown. If you click on that icon, the TortoiseSVN checkout dialog is started for this URL. | 2529 | File xsl dari repositori TortoiseSVN memiliki trik yang bagus: jika Anda menjelajah repositori dengan penjelajah web Anda, setiap folder dalam repositori Anda memiliki suatu ikon di kanannya. Jika Anda mengeklik ikon tersebut, dialog checkout TortoiseSVN akan dijalankan untuk URL ini. |
| 72 | - | A short explanation of what you just entered: |
2535 | Penjelasan singkat dari apa yang baru Anda masukkan: |
| 73 | - | If you used the |
2551 | Jika Anda menggunakan direktif SVNParentPath maka Anda tidak harus mengubah file konfig Apache setiap kali Anda menambah repositori Subversion baru. Cukup buat repositori baru dibawah lokasi yang sama seperti repositori pertama dan Anda selesai! Dalam perusahaan saya, Saya mempunyai akses langsung ke folder tertentu itu pada server via SMB (akses file normal windows). Maka Saya cukup membuat folder baru disana, jalankan perintah TortoiseSVN |
| 74 | - | The |
2572 | Modul mod_authz_svn membolehkan kontrol fine-grained dari perizinan akses berdasarkan nama pengguna dan path repositori. Ini tersedia dengan server Apache, dan sejak Subversion 1.3 itu tersedia juga dengan svnserve. |
| 75 | - | Authentication and authorization are separate processes. If a user wants to gain access to a repository path, she has to meet |
2646 | Otentikasi dan otorisasi adalah proses terpisah. Jika seorang pengguna ingin mendapatkan akses ke suatu path repositori, dia harus memenuhi |
| 76 | - | But there's a solution for that problem - at least if you're accessing the repository from inside a LAN with a windows domain controller: |
2672 | Tapi ada solusi untuk masalah itu - setidaknya jika Anda mengakses repositori dari dalam LAN dengan kontroler domain windows: mod_auth_sspi! |
| 77 | - | The original SSPI module was offered by Syneapps including source code. But the development for it has been stopped. But don't despair, the community has picked it up and improved it. It has a new home on |
2687 | Modul original SSPI ditawarkan oleh Syneapps termasuk kode sumber. Tapi pengembangan untuk itu telah dihentikan. Tapi jangan putus asa, komunitas telah mengambil dan meningkatkannya. Ia mempunyai rumah baru di |
| 78 | - | Download the module which matches your apache version, then copy the file |
2693 | Unduh modul tersebut, salin file |
| 79 | - | Edit the Apache config file: add the line LoadModule sspi_auth_module modules/mod_auth_sspi.so\n LoadModule auth_module modules/mod_auth.so\n |
2699 | Edit file konfig Apache: tambahkan baris LoadModule sspi_auth_module modules/mod_auth_sspi.so\n LoadModule auth_module modules/mod_auth.so\n |
| 80 | - | To make the Subversion location use this type of authentication you have to change the line AuthType Basic\n AuthType SSPI\n SSPIAuth On\n SSPIAuthoritative On\n SSPIDomain <domaincontroller>\n SSPIOmitDomain on\n SSPIUsernameCase lower\n SSPIPerRequestAuth on\n SSPIOfferBasic On\n |
2715 | Untuk membuat lokasi Subversion menggunakan tipe otentikasi ini Anda harus mengubah baris AuthType Basic\n AuthType SSPI\n SSPIAuth On\n SSPIAuthoritative On\n SSPIDomain <domaincontroller>\n SSPIOmitDomain on\n SSPIUsernameCase lower\n SSPIPerRequestAuth on\n SSPIOfferBasic On\n |
| 81 | - | Note that if you are authenticating using SSPI, then you don't need the |
2747 | Catatan bahwa jika Anda mengotentikasi menggunakan SSPI, maka Anda tidak memerlukan baris |
| 82 | - | Subversion |
2761 | File Subversion AuthzSVNAccessFile adalah sensitif huruf dalam hubungannya dengan nama-nama pengguna (\"JUser\" berbeda dari \"juser\"). |
| 83 | - | In Microsoft's world, Windows domains and user names are not case sensitive. Even so, some network administrators like to create user accounts in CamelCase (e.g. |
2767 | Dalam dunia Microsoft, Windows domain dan nama pengguna tidak sensitif huruf. Meskipun demikian, beberapa administrator jaringan seperti untuk membuat akun pengguna dalam CamelCase (contoh. \"JUser\"). |
| 84 | - | The end result is that you may need at least two entries in your |
2778 | Hasil akhir adalah bahwa Anda memerlukan setidaknya dua entri dalam AuthzSVNAccessFile untuk setiap pengguna -- entri huruf kecil dan entri dalam huruf sama dengan yang dioper Internet Explorer ke Apache. Anda juga perlu untuk melatih pengguna Anda untuk mengetik dalam mandatnya menggunakan huruf kecil ketika mengakses repositori via TortoiseSVN. |
| 85 | - | Apache's Error and Access logs are your best friend in deciphering problems such as these as they will help you determine the username string passed onto Subversion's |
2784 | Log Kesalahan dan Akses Apache adalah teman terbaik Anda dalam mengatasi masalah seperti ini karena mereka akan membantu Anda memeriksa string nama pengguna yang dioper ke dalam modul Subversion's AuthzSVNAccessFile. Anda perlu bereksperiman dengan format pasti dari string pengguna dalam svnaccessfile (contoh. |
| 86 | - | To enable both Windows domain and AuthBasicAuthoritative Off\n SSPIAuthoritative Off\n |
2810 | Untuk menghidupkan baik otentikasi Windows domain maupun file passwd, tambahkan entri berikut di dalam blok AuthAthoritative Off\n SSPIAuthoritative Off\n |
| 87 | - | Here is an example of the full Apache configuration for combined Windows domain and <Location /svn>\n DAV svn\n SVNListParentPath on\n SVNParentPath D:\\SVN\n \n AuthName \"Subversion repositories\"\n AuthzSVNAccessFile svnaccessfile.txt\n \n # NT Domain Logins.\n AuthType SSPI\n SSPIAuth On\n SSPIAuthoritative Off\n SSPIDomain <domaincontroller>\n SSPIOfferBasic On\n \n # Htpasswd Logins.\n AuthType Basic\n AuthBasicAuthoritative Off\n AuthUserFile passwd\n \n Require valid-user\n </Location>\n |
2824 | Ini adalah contoh dari konfigurasi penuh Apache untuk mengkombinasikan otentikasi Windows domain dan file <Location /svn>\n DAV svn\n SVNListParentPath on\n SVNParentPath D:\\SVN\n \n AuthName \"Subversion repositories\"\n AuthzSVNAccessFile svnaccessfile.txt\n \n # NT Domain Logins.\n AuthType SSPI\n SSPIAuth On\n SSPIAuthoritative Off\n SSPIDomain <domaincontroller>\n SSPIOfferBasic On\n \n # Htpasswd Logins.\n AuthType Basic\n AuthAuthoritative Off\n AuthUserFile passwd\n \n Require valid-user\n </Location>\n |
| 88 | - | Next you need to create an SSL certificate. To do that open a command prompt (DOS-Box) and change to the Apache folder (e.g. bin\\openssl req -config conf\\openssl.cnf -new -out my-server.csr\n |
2906 | Berikutnya Anda perlu membuat sertifikat SSL. Untuk melakukan itu buka prompt perintah (Kotak-DOS) dan ubah ke folder apache (contoh. bin\\openssl req -config bin\\openssl.cnf -new -out my-server.csr\n |
| 89 | - | Normally the bin\\openssl genrsa -out conf\\privkey.pem 2048\n |
2918 | Biasanya file bin\\openssl genrsa -out privkey.pem 2048\n |
| 90 | - | Next type the commands bin\\openssl rsa -in conf\\privkey.pem -out conf\\server.key\n bin\\openssl req -new -key conf\\server.key -out conf\\server.csr \\\n -config conf\\openssl.cnf\n bin\\openssl x509 -in conf\\server.csr -out conf\\server.cert\n -req -signkey conf\\server.key -days 4000\n bin\\openssl x509 -in conf\\server.cert -out conf\\server.der.crt\n -outform DER\n |
2930 | Selanjutnya ketik perintah bin\\openssl rsa -in privkey.pem -out my-server.key\n bin\\openssl x509 -in my-server.csr -out my-server.cert\n -req -signkey my-server.key -days 4000\n bin\\openssl x509 -in my-server.cert -out my-server.der.crt -outform DER\n |
| 91 | - | define a separate |
2976 | mendefinisikan direktif <Location /path> terpisah dalam file konfig apache, dan tambah |
| 92 | - | In the SSL \"standard\" setup there's often the following statement in Apache's virtual SSL host: SetEnvIf User-Agent \".*MSIE.*\" \\\n nokeepalive ssl-unclean-shutdown \\\n downgrade-1.0 force-response-1.0\n |
2987 | Dalam penyiapan ssl \"standar\" sering ada pernyataan berikut dalam host ssl virtual apache: SetEnvIf User-Agent \".*MSIE.*\" \\\n nokeepalive ssl-unclean-shutdown \\\n downgrade-1.0 force-response-1.0\n |
| 93 | - | When you've set up SSL to make your repository more secure, you might want to disable the normal access via non-SSL (http) and only allow https access. To do this, you have to add another directive to the Subversion |
3013 | Ketika Anda telah menyiapkan SSL untuk membuat repositori Anda lebih aman, Anda mungkin ingin mematikan akses normal via non-ssl (http) dan hanya membolehkan akses https. Untuk melakukan ini, Anda harus menambah direktif lain ke Subversion <Location> blok: |
| 94 | - | An example <Location /svn>\n DAV svn\n SVNParentPath D:\\SVN\n SSLRequireSSL\n AuthType Basic\n AuthName \"Subversion repositories\"\n AuthUserFile passwd\n #AuthzSVNAccessFile svnaccessfile\n Require valid-user\n </Location>\n |
3019 | Contoh blok <Location> akan terlihat seperti ini: <Location /svn>\n DAV svn\n SVNParentPath D:\\SVN\n SSLRequireSSL\n AuthType Basic\n AuthName \"Subversion repositories\"\n AuthUserFile passwd\n #AuthzSVNAccessFile svnaccessfile\n Require valid-user\n </Location>\n |
| 95 | - | Some common operations have well-known Windows shortcuts, but do not appear on buttons or in menus. If you can't work out how to do something obvious, like refreshing a view, check here. |
3287 | Beberapa operasi umum mempunyai jalan pintas Windows yang dikenal-baik, tapi tidak nampak pada tombol atau dalam menu. Jika Anda tidak bisa mengetahui bagaimana melakukan sesuatu dengan jelas, seperti menyegarkan tampilan, periksa disini. |
| 96 | - | authentication cache | 3298 | otentikasi |
| 97 | - | 3309 | ||
| 98 | - | If the repository that you are trying to access is password protected, an authentication Dialog will show up. |
3325 | Jika repositori yang sedang Anda coba akses dilindungi kata sandi, Dialog otentikasi akan muncul. |
| 99 | - | If you want to clear the authentication cache for all servers, you can do so from the |
3331 | Jika Anda ingin membersihkan tembolok otentikasi untuk |
| 100 | - | add files to repository | 3376 | Item yang ditambahkan ke repositori. |
| 101 | - | It is easy to import to the wrong folder level in the repository. | 3407 | Gunakan browser repositori untuk membuat folder baru secara langsung dalam repositori. |
| 102 | - | Organize the files in folders and sub-folders. Although it is possible to rename/move files later it is highly recommended to get your project's structure straight before importing! | 3422 | Atur file dalam folder dan subfolder. Meskipun ini mungkin untuk mengganti nama/memindahkan file nantinya sangat direkomendasikan untuk mendapatkan struktur proyek langsung sebelum mengimpor! |
| 103 | - | As soon as you press |
3462 | Segera setelah Anda menekan |
| 104 | - | In such cases we suggest to use |
3513 | Dalam kasus demikian kami sarankan untuk menggunakan file |
| 105 | - | create working copy | 3539 | copy pekerjaan |
| 106 | - | Checkout Depth | 3560 | Checkout |
| 107 | - | Fully recursive | 3565 | /nonrecursive |
| 108 | - | Only this item | 3591 | Item-item lainnya. |
| 109 | - | In the repository browser, |
3628 | Jika Anda ingin membandingkan dua revisi dalam histori file, misalnya revisi 100 dan 200 dari file yang smaa, cukup gunakan |
| 110 | - | Select the new folder and use |
3646 | Untuk menguji apakah svnserve bekerja, gunakan |
| 111 | - | Changing working copy depth | 3664 | Merelokasi copy pekerjaan |
| 112 | - | Once you have checked out a working copy to a particular depth you can change that depth later to get more or less content using |
3670 | Dalam copy pekerjaan Anda pilih |
| 113 | - | If |
3689 | Jika opsi-opsi ini dicentang, Anda harus melakukan pemutahiran ke copy pekerjaan Anda menggunakan |
| 114 | - | It is recommended that you check out only the |
3695 | Direkomendasikan bahwa Anda melakukan check out hanya bagian |
| 115 | - | send changes | 3721 | Memulihkan Perubahan |
| 116 | - | check in | 3727 | link checkout |
| 117 | - | If you think that the commit dialog shows you too many unversioned (e.g. compiler generated or editor backup) files, there are several ways to handle this. You can: |
3794 | Jika Anda mengira bahwa dialog komit TSVN memperlihatkan kepada Anda terlalu banyak file tidak berversi (contoh: yang dihasilkan kompilator atau cadangan editor), ada beberapa cara untuk mengatasi ini. Anda bisa: |
| 118 | - | 3800 | ||
| 119 | - | Repairing External Copies | 3838 | |
| 120 | - | If you made a copy of a file but forgot to use the Subversion command to do so, you can repair that copy so the new file doesn't lose its history. Simply select both the old name (normal or modified) and the new name (unversioned) and use |
3844 | Terkadang file-file diubah namanya di luar Subversion, dan mereka muncul di daftar file sebagai file yang hilang dan file yang tidak terversi. Untuk menghindari kehilangan sejarah tersebut, Anda perlu untuk memberitahu Subversion tentang koneksi tersebut. Cukup pilih nama lama (hilang) dan nama baru (tidak terversi) dan gunakan |
| 121 | - | The log message window also includes a filename and function auto-completion facility. This uses regular expressions to extract class and function names from the (text) files you are committing, as well as the filenames themselves. If a word you are typing matches anything in the list (after you have typed at least 3 characters, or pressed |
3896 | Jendela log pesan menyertakan nama file dan fungsi fasilitas otomatis-lengkap. Ini menggunakan ekspresi reguler untuk mengurai kelas dan nama fungsi dari file (teks) yang Anda komit, juga sebagai nama file itu sendiri. Jika kata yang Anda ketik sama dengan apa yang ada dalam daftar (setelah Anda mengetikan setidaknya 3 karakter), drop-down muncul membolehkan Anda untuk memilih nama penuh. Ekspresi reguler disertakan dengan TortoiseSVN disimpan dalam folder instalasi TortoiseSVN |
| 122 | - | If you want to include the checked paths in your log message, you can use the command |
3910 | Jika Anda |
| 123 | - | Integration with Bug Tracking Tools | 3930 | Integrasi dengan Piranti Bugtracking |
| 124 | - | If you have activated the bug tracking system, you can set one or more Issues in the |
3936 | Jika Anda telah mengaktifkan sistem bugtracking, Anda bisa mengeset satu atau lebih Isu dalam kotak teks |
| 125 | - | fetch changes | 4027 | ekspor perubahan |
| 126 | - | 4038 | ||
| 127 | - | If you get any |
4086 | Jika Anda mendapatkan |
| 128 | - | When the update is complete, the progress dialog shows a summary of the number of items updated, added, removed, conflicted, etc. below the file list. This summary information can be copied to the clipboard using |
4092 | Ketika pemutahiran selesai, dialog kemajuan menampilkan ringkasan dari jumlah item yang dimutahirkan, ditambahkan, dihapus, berkonflik, dll. di bawah daftar file. Ringkasan informasi ini bisa disalin ke clipboard menggunakan |
| 129 | - | The standard Update command has no options and just updates your working copy to the HEAD revision of the repository, which is the most common use case. If you want more control over the update process, you should use |
4098 | Perintah Pemutahiran standar tidak mempunyai opsi dan hanya memutahirkan copy pekerjaan Anda ke revisi HEAD pada repositori, yang mana adalah penggunaan yang paling umum. Jika Anda ingin lebih mengontrol proses pemutahiran, Anda harus menggunakan |
| 130 | - | If you update a file or folder to a specific revision, you should not make changes to those files. You will get out of dateerror messages when you try to commit them! If you want to undo changes to a file and start afresh from an earlier revision, you can rollback to a previous revision from the revision log dialog. Take a look at |
4104 | Jika Anda memutahirkan file atau folder ke revisi tertentu, Anda jangan membuat perubahan pada file itu. Anda akan mendapatkan pesan kesalahan |
| 131 | - | 4110 | ||
| 132 | - | If you simply want a local copy of an old version of a file it is better to use the |
4116 | Jika Anda |
| 133 | - | tree conflict | 4157 | konflik |
| 134 | - | resolve | 4163 | Selesaikan |
| 135 | - | file conflicts | 4169 | konflik |
| 136 | - | tree conflicts | 4179 | konflik |
| 137 | - | File Conflicts | 4193 | Edit Konflik |
| 138 | - | A file conflict occurs when two or more developers have changed the same few lines of a file. As Subversion knows nothing of your project, it leaves resolving the conflicts to the developers. Whenever a conflict is reported, you should open the file in question, and search for lines starting with the string \t<<<<<<< filename\n \t\tyour changes\n \t=======\n \t\tcode merged from repository\n \t>>>>>>> revision\n \t |
4229 | Suatu saat, Anda akan menghadapi <<<<<<< filename\n your changes\n =======\n code merged from repository\n >>>>>>> revision\n |
| 139 | - | Tree Conflicts | 4269 | konflik |
| 140 | - | Developer A moves |
4324 | Gunakan direktori \"_svn\" daripada \".svn\" |
| 141 | - | For a folder conflict: |
4367 | Ini tidak berlaku jika: |
| 142 | - | Developer A moves |
4390 | Gunakan direktori \"_svn\" daripada \".svn\" |
| 143 | - | Developer B moves |
4396 | Buat folder lain |
| 144 | - | view changes | 4538 | ekspor perubahan |
| 145 | - | working copy status | 4544 | copy pekerjaan |
| 146 | - | 4571 | ||
| 147 | - | 4577 | ||
| 148 | - | 4583 | ||
| 149 | - | 4589 | ||
| 150 | - | 4595 | ||
| 151 | - | 4601 | ||
| 152 | - | 4607 | ||
| 153 | - | 4613 | ||
| 154 | - | In fact, you may find that not all of these icons are used on your system. This is because the number of overlays allowed by Windows is very limited and if you are also using an old version of TortoiseCVS, then there are not enough overlay slots available. TortoiseSVN tries to be a Good Citizen (TM)and limits its use of overlays to give other apps a chance too. |
4623 | Kenyataannya, Anda mungkin menemukan bahwa tidak semua ikon ini digunakan pada sistem Anda. Ini dikarenakan jumlah lapisan yang dibolehkan oleh Windows dibatasi hanya 15. Windows menggunakan 4 dari itu, dan sisanya 11 bisa digunakan oleh aplikasi lain. Jika Anda juga menggunakan TortoiseCVS, maka slot lapisan ikon tidak cukup tersedia, maka TortoiseSVN mencoba menjadi Warga Yang Baik (TM)dan membatasi penggunaan lapisan untuk memberikan kesempatan bagi aplikasi lain. |
| 155 | - | Simply right click on one of the headings of a column, choose Detailed View. Scroll down until the entries starting with SVN come into view. Check the ones you would like to have displayed and close the dialog by pressing |
4652 | Cukup klik kanan pada salah satu judul kolom, pilih |
| 156 | - | If you click on the |
4688 | Jika Anda mengklik |
| 157 | - | You can also revert changes in individual files. If you have deleted a file accidentally, it will show up as |
4734 | Anda juga bisa memulihkan perubahan dalam file individual. Jika Anda telah menghapus file secara tidak sengaja, ia akan ditampilkan sebagai |
| 158 | - | The changelist feature in TortoiseSVN is only available in Windows XP and later, as it depends on a shell capability which is not present in Windows 2000. Sorry, but Win2K is really quite old now, so please don't complain. | 4802 | Fitur daftar perubahan hanya ada di Windows XP atau yang lebih baru karena fitur itu bergantung pada kemampuan shell yang tidak ada di Windows 2000. Maaf, Win2K sekarang benar-benar tua, jadi janganlah mengeluh. |
| 159 | - | Select one or more files and use |
4811 | Gunakan |
| 160 | - | 4825 | Selain memberi indikasi visual langsung dari pengelompokan, Anda juga dapat menggunakan judul kelompok untuk memilih file mana saja yang akan dikomit. | |
| 161 | - | Changelists are purely a local client feature. Creating and removing changelists will not affect the repository, nor anyone else's working copy. They are simply a convenient way for you to organise your files. | 4842 | Daftar-daftar perubahan adalah murni fitur klien lokal. Membuat dan menghapus daftar-daftar perubahan tidak akan memengaruhi repositori ataupun klien lain. |
| 162 | - | commit messages | 4863 | Pesan Log Komit |
| 163 | - | log messages | 4869 | log pesan |
| 164 | - | Revision Log Actions | 4939 | Dialog Log Revisi |
| 165 | - | 4953 | ||
| 166 | - | 4959 | ||
| 167 | - | Compare with working copy | 4979 | copy pekerjaan |
| 168 | - | Compare and blame with working BASE | 4990 | Bandingkan dan Blame dengan BASE Pekerjaan |
| 169 | - | Blame the selected revision, and the file in your working BASE and compare the blame reports using a visual diff tool. Read |
4996 | Blame revisi yang dipilih, dan file dalam BASE pekerjaan Anda dan membandingkan hasil menggunakan piranti diff visual. Baca |
| 170 | - | Show changes as unified diff | 5002 | Peninjau Unified Diff |
| 171 | - | Compare with previous revision | 5013 | Perbedaan antara dua revisi sebelumnya |
| 172 | - | Compare the selected revision with the previous revision. This works in a similar manner to comparing with your working copy. For folders this option will first show the changed files dialog allowing you to select files to compare. | 5018 | Membandingkan revisi terpilih dengan revisi sebelumnya. Ini bekerja dalam cara yang mirip dengan membandingkan dengan copy pekerjaan Anda. |
| 173 | - | Compare and blame with previous revision | 5024 | Bandingkan dan Blame dengan BASE Pekerjaan |
| 174 | - | 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). | 5030 | Blame revisi yang dipilih, dan revisi sebelumnya, dan bandingkan hasilnya dengan suatu alat diff visual. |
| 175 | - | Save revision to... | 5037 | revisi |
| 176 | - | Save the selected revision to a file so you have an older version of that file. (files only). | 5043 | Menyimpan revisi yang dipilih ke file agar Anda mempunyai versi lama dari file itu. |
| 177 | - | Open the selected file, either with the default viewer for that file type, or with a program you choose. (files only). | 5054 | Membuka file yang dipilih, baik dengan peninjau standar untuk tipe file itu, ataupun dengan program yang Anda sukai. |
| 178 | - | Blame... | 5061 | Blame |
| 179 | - | Browse repository | 5071 | Melihat Repositori |
| 180 | - | Open the repository browser to examine the selected file or folder in the repository as it was at the selected revision. | 5077 | Membuka browser repositori untuk memeriksa folder yang dipilih. Opsi ini hanya tersedia saat Anda mengakses log untuk direktori. |
| 181 | - | Create branch/tag from revision | 5083 | Menggabungkan Suatu Jangkauan Revisi |
| 182 | - | Create a branch or tag from a selected revision. This is useful e.g. if you forgot to create a tag and already committed some changes which weren't supposed to get into that release. | 5089 | Membuat cabang/tag dari revisi yang dipilih. Ini berguna misalnya jika Anda lupa untuk membuat tag dan sudah mengkomit beberapa perubahan yang tidak seharusnya masuk ke dalam rilis itu. |
| 183 | - | Update item to revision | 5095 | Mutahirkan ke revisi |
| 184 | - | Update your working copy to the selected revision. Useful if you want to have your working copy reflect a time in the past, or if there have been further commits to the repository and you want to update your working copy one step at a time. It is best to update a whole directory in your working copy, not just one file, otherwise your working copy could be inconsistent. | 5101 | Memutahirkan copy pekerjaan Anda ke revisi yang dipilih. Berguna jika Anda ingin mempunyai copy pekerjaan Anda merefleksikan waktu yang lalu. Hal terbaik untuk memutahirkan seluruh direktori dalam copy pekerjaan Anda, buka hanya satu file, sebaliknya copy pekerjaan Anda menjadi tidak konsisten dan Anda tidak akan bisa mengkomit setiap perubahan. |
| 185 | - | Revert to this revision | 5111 | Mutahirkan ke revisi |
| 186 | - | 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. The changes are undone in your working copy so this operation does |
5117 | Memulihkan ke revisi sebelumnya. Jika Anda membuat beberapa perubahan, dan kemudian memutuskan bahwa Anda benar-benar ingin kembali ke revisi N, ini adalah perintah yang Anda perlukan. Lagi, perubahan-perubahan dipulihkan dalam salinan pekerjaan Anda, jadi operasi ini |
| 187 | - | Revert changes from this revision | 5141 | Perbedaan dari revisi sebelumnya |
| 188 | - | Undo changes from which were made in the selected revision. The changes are undone in your working copy so this operation does |
5147 | Memulihkan perubahan dimana Anda buat dalam revisi yang dipilih. Perubahan dipulihkan dalam copy pekerjaan Anda, jadi operasi ini |
| 189 | - | Merge revision to... | 5161 | revisi |
| 190 | - | Checkout... | 5171 | Checkout |
| 191 | - | Export... | 5181 | Ekspor |
| 192 | - | Edit author / log message | 5191 | Font untuk pesan log |
| 193 | - | Show revision properties | 5202 | Properti Subversion |
| 194 | - | Search log messages... | 5222 | log pesan |
| 195 | - | Compare revisions | 5242 | membandingkan revisi-revisi |
| 196 | - | Blame revisions | 5258 | Revisi Blame |
| 197 | - | Blame the two revisions and compare the blame reports using a visual difference tool. Read |
5264 | Blame dua revisi dan bandingkan hasil menggunakan piranti pembeda visual. Baca selengkapnya |
| 198 | - | If you select two or more revisions (using the usual |
5294 | Jika Anda memilih multipel revisi berturut-turut (menggunakan |
| 199 | - | Show changes | 5313 | ekspor perubahan |
| 200 | - | Show changes made in the selected revision for the selected file. This context menu is only available for files shown as |
5319 | Menampilkan perbedaan yang dibuat dalam revisi yang dipilih untuk file yang dipilih. Menu konteks ini hanya tersedia untuk file yang ditampilkan sebagai |
| 201 | - | Blame changes | 5325 | Memulihkan Perubahan |
| 202 | - | Blame the selected revision and the previous revision for the selected file, and compare the blame reports using a visual diff tool. Read |
5331 | Blame revisi yang dipilih dan revisi sebelumnya untuk file yang dipilih, dan menampilkan perbedaan menggunakan piranti diff visual. Baca selengkapnya |
| 203 | - | Show as unified diff | 5337 | Peninjau Unified Diff |
| 204 | - | Show file changes in unified diff format. This context menu is only available for files shown as |
5343 | Menampilkan perbedaan yang dibuat dalam revisi yang dipilih untuk file yang dipilih. Menu konteks ini hanya tersedia untuk file yang ditampilkan sebagai |
| 205 | - | Show properties | 5364 | properti |
| 206 | - | Show log | 5375 | Tampilkan Log |
| 207 | - | Get merge logs | 5386 | Gunakan dialog gabung |
| 208 | - | 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 |
5431 | Untuk repositori besar disana mungkin ada ratusan atau bahkan ribuan perubahan dan mengambil itu semua bisa memerlukan waktu lama. Biasanya Anda hanya tertarik pada perubahan yang lebih baru. Standarnya, jumlah pesan log yang diambil dibatasi ke 100, tapi Anda bisa mengubah nilai ini dalam |
| 209 | - | Current Working Copy Revision | 5482 | Melakukan Checkout Copy Pekerjaan |
| 210 | - | merge tracking log | 5500 | bugtracking |
| 211 | - | revision properties | 5532 | Properti Subversion |
| 212 | - | revprops | 5538 | repobrowser |
| 213 | - | Subversion 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 |
5553 | Subversion membiarkan Anda mengubah kedua pesan log serta pembuat dari revisi kapan saja Anda inginkan. Tapi karena perubahan itu tidak bisa dibatalkan (perubahan itu tidak diversi) standarnya fitur ini dimatikan. Untuk membuat ini bekerja Anda harus menyiapkan hook pre-revprop-change. Silahkan rujuk ke bab pada |
| 214 | - | 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. | 5559 | Sekali Anda telah menyiapkan server Anda dengan hook yang dibutuhkan, Anda bisa mengubah pembuat dan pesan log dari setiap revisi, menggunakan menu konteks dari pane atas dari dialog Log. |
| 215 | - | You can also filter the path names in the bottom pane using the |
5602 | Anda bisa juga menyaring nama path dalam pane bawah menggunakan kotak centang |
| 216 | - | No Log Formatting from Repository Browser | 5612 | Browser Repositori |
| 217 | - | Where there are a few major authors and many minor contributors, the number of tiny segments can make the graph more difficult to read. The slider at the bottom allows you to set a threshold (as a percentage of total commits) below which any activity is grouped into an |
5667 | Dimana ada beberapa pembuat utama dan banyak kontributor minor, jumlah segmen kecil bisa membuat grafik lebih sulit untuk dibaca. Penggulung di bawah membolehkan Anda untuk mengeset threshold (sebagai prosentase dari total komit) dibawah yang setiap aktivitas dikelompokan ke dalam kategori |
| 218 | - | By default the analysis is case-sensitive, so users |
5693 | Standarnya analisis adalah sensitif huruf, maka pengguna |
| 219 | - | Here you have three options: |
5740 | Membuat repositori dalam |
| 220 | - | compare | 5774 | bandingkan file |
| 221 | - | One of the commonest requirements in project development is to see what has changed. You might want to look at the differences between two revisions of the same file, or the differences between two separate files. TortoiseSVN provides a built-in tool named |
5780 | Salah satu kebutuhan yang paling umum dalam pengembangan proyek adalah untuk melihat apa yang telah berubah. Anda mungkin ingin melihat perbedaan antara dua revisi dari file yang sama, atau perbedaan antara dua file terpisah. TortoiseSVN menyediakan piranti builtin yang dinamai |
| 222 | - | If you want to see the differences between a file in your working copy, and a file in any Subversion repository, you can do that directly in explorer by selecting the file then holding down the |
5870 | Jika Anda ingin melihat perbedaan antara file dalam copy pekerjaan Anda, dan file dalam setiap repositori Subversion, Anda bisa melakukan itu secara langsung dalam explorer dengan memilih file lalu menekan terus tombol |
| 223 | - | The built-in tools supplied with TortoiseSVN do not support viewing differences between directory hierarchies. But if you have an external tool which does support that feature, you can use that instead. In |
5891 | Piranti builtin yang disertakan dengan TortoiseSVN tidak mendukung untuk melihat perbedaan antara hirarki direktori. Tapi jika Anda mempunyai piranti eksternal yang mendukung fitur itu, Anda bisa menggunakannya. Dalam |
| 224 | - | You can also export the |
5963 | Anda juga dapat lompat ke suatu baris spesifik menggunakan |
| 225 | - | If you want to export the list of files |
5969 | Jika Anda ingin mengekspor daftar file |
| 226 | - | 6013 | ||
| 227 | - | Naturally you can also zoom in and out and pan around the image. You can also pan the image simply by left-dragging it. If you select the |
6019 | Secara alami, Anda juga dapat membesarkan dan mengecilkan dan menggeser gambar. Anda juga dapat menggeser gambar cukup dengan menyeret-kiri gambar tersebut. Jika Anda memilih opsi |
| 228 | - | An image info box shows details about the image file, such as the size in pixels, resolution and colour depth. If this box gets in the way, use |
6025 | Dalam kotak info gambar menampilkan detil file gambar, seperti ukuran dalam pixel, resolusi dan kedalaman warna. Jika kotak ini berjalan, gunakan |
| 229 | - | Araxis Merge is a useful commercial tool for diff and merging both files and folders. It does three-way comparison in merges and has synchronization links to use if you've changed the order of functions. Download it from |
6118 | Araxis Merge adalah piranti komersil untuk diff dan penggabungan file dan folder. Ia melakukan perbandingan tiga-cara dalam merge dan mempunyai link sinkronisasi untuk digunakan jika Anda telah mengubah urutan fungsi. Download ini dari |
| 230 | - | version new files | 6159 | Properti Subversion |
| 231 | - | You can also use the Add command on already versioned folders. In that case, the add dialog will show you all unversioned files inside that versioned folder. This helps if you have many new files and need to add them all at once. | 6186 | Anda juga bisa menggunakan perintah Tambah pada folder yang sudah berversi. Dalam kasus itu, dialog tambah akan memperlihatkan kepada Anda file-file tidak berversi di dalam folder yang berversi. Ini membantu jika Anda mempunyai banyak file baru dan perlu menambahkannya sekaligus. |
| 232 | - | If you add a file or folder by mistake, you can undo the addition before you commit using |
6223 | Dalam copy pekerjaan Anda pilih |
| 233 | - | copy files | 6233 | bandingkan file |
| 234 | - | You can copy files and folders from your working copy to another location in the repository using |
6273 | Anda ingin menukar ke cabang berbeda atau direktori di dalam repositori yang sama. Untuk melakukan itu Anda harus menggunakan |
| 235 | - | You can locate an older version of a file or folder in the log dialog and copy it to a new location in the repository directly from the log dialog using |
6279 | Anda ingin menukar ke cabang berbeda atau direktori di dalam repositori yang sama. Untuk melakukan itu Anda harus menggunakan |
| 236 | - | Cannot copy between repositories | 6289 | repositori eksternal |
| 237 | - | unversioned files/folders | 6313 | File/folder yang dihapus |
| 238 | - | 6319 | ||
| 239 | - | No Paths in Global Ignore List | 6419 | Daftar Abaikan global |
| 240 | - | Deleting, Moving and Renaming | 6429 | Menghapus, Mengganti Nama Dan Memindahkan |
| 241 | - | Deleting files and folders | 6445 | File/folder yang dihapus |
| 242 | - | Use |
6461 | |
| 243 | - | When you deletedicon overlay. Up until you commit the change, you can get the file back using |
6467 | Jika Anda menghapus file/direktori menggunakan TSVN, file dihapus dari copy pekerjaan Anda dan ditandai untuk penghapusan. Folder leluhurnya memperlihatkan lapisan ikon \"dihapus\". Anda bisa selalu mendapatkan file kembali, jika Anda memanggil |
| 244 | - | When you |
6472 | Jika Anda melakukan |
| 245 | - | If you want to delete an item from the repository, but keep it locally as an unversioned file/folder, use |
6477 | Jika Anda ingin menghapus sesuatu dari repositori tetapi menginginkan untuk mempertahankannya secara lokal sebagai file/folder tak berversi, gunakan |
| 246 | - | Moving files and folders | 6503 | Komit file atau folder? |
| 247 | - | If you want to do a simple in-place rename of a file or folder, use |
6521 | Jika Anda |
| 248 | - | If you want to move files around inside your working copy, perhaps to a different sub-folder, use the right-mouse drag-and-drop handler: |
6537 | Jika Anda ingin memindahkan file didalam copy pekerjaan, gunakan pengendali drag-dan-drop lagi: |
| 249 | - | Since renames and moves are done as a delete followed by an add you must commit the parent folder of the renamed/moved file so that the deleted part of the rename/move will show up in the commit dialog. If you don't commit the removed part of the rename/move, it will stay behind in the repository and when your co-workers update, the old file will not be removed. i.e. they will have |
6548 | Karena mengganti nama dan memindahkan dikerjakan sebagai penghapusan diikuti oleh penambahan, Anda harus mengkomit folder leluhur dari file yang diganti nama/dipindahkan akan muncul dalam dialog komit. Jika Anda tidak mengkomit bagian yang dihapus dari ganti nama/pindahkan, ia akan tetap dalam repositori dan pemutahiran dari co-worker Anda tidak akan menghapus file lama. Misalnya mereka akan mempunyai |
| 250 | - | You can also use the repository browser to move items around. Read |
6559 | TortoiseSVN juga dapat berintegrasi dengan beberapa browser repositori berbasis web. Baca |
| 251 | - | case change | 6579 | Perubahan lokal |
| 252 | - | Fortunately there are (at least) two possible methods to rename a file without losing its log history. It is important to rename it within subversion. Just renaming in the explorer will corrupt your working copy! | 6589 | Ada (setidaknya) dua kemungkinan solusi untuk mengganti nama file tanpa kehilangan histori lognya. Ini penting untuk mengganti nama di dalam Subversion. Mengganti nama dalam explorer akan merusak copy pekerjaan Anda!!! |
| 253 | - | If the repository already contains two files with the same name but differing only in case (e.g. |
6640 | Seandainya Anda mempunyai dua file dalam repositori dengan nama yang sama tapi dibedakan hanya jenis huruf (contoh. TEST.TXT dan test.txt) Anda tidak bisa memutahirkan atau checkout direktori dimana file itu berada lagi. |
| 254 | - | clean | 6710 | membersihkan |
| 255 | - | If you want to undo the addition of an item, this appears in the context menu as |
6730 | Jika Anda belum mengkomit penambahan, maka yang harus Anda lakukan adalah menggunakan |
| 256 | - | Revert is Slow | 6756 | Dialog Pulihkan |
| 257 | - | Cleanup has another useful side effect. If a file date changes but its content doesn't, Subversion cannot tell whether it has really changed except by doing a byte-by-byte comparison with the pristine copy. If you have a lot of files in this state it makes acquiring status very slow, which will make many dialogs slow to respond. Executing a Cleanup on your working copy will repair these brokentimestamps and restore status checks to full speed. |
6784 | Bersihkan mempunyai efek samping berguna lain. Jika tanggal file berubah tetapi isinya tidak, Subversion tidak bisa mengatakan apakah ia benar-benar berubah kecuali dengan melakukan perbandingan byte-demi-byte dengan copy murni. Jika Anda mempunyai banyak file dalam kondisi ini membuat permintaan status sangat lambat, yang akan membuat banyak dialog lambat merespon. Menjalankan Pembersihan pada copy pekerjaan Anda akan mereparasi cap waktu yang rusakini dan menyimpan kembali status periksa ke kecepatan penuh. |
| 258 | - | Subversion properties | 6825 | Properti Subversion |
| 259 | - | 6836 | ||
| 260 | - | You can add your own properties, or some properties with a special meaning in Subversion. These begin with |
6842 | Anda bisa menambahkan properti Anda sendiri, atau beberapa properti dengan arti khusus dalam Subversion. Ini dimulai dengan |
| 261 | - | keywords | 6853 | Kata Kunci |
| 262 | - | The full URL of this file in the repository. | 6875 | Judul jendela untuk file dalam repositori |
| 263 | - | To find out how to use these keywords, look at the |
6889 | Adalah penting untuk mengerti bagaimana mencabangkan dan menggabung pekerjaan dalam Subversion sebelum Anda mulai menggunakannya, karena ini bisa menjadi sedikit rumit. Sangat direkomendasikan bahwa Anda sudah membaca bab |
| 264 | - | For more information about properties in Subversion see the |
6895 | Informasi selanjutnya mengenai svnserve bisa ditemukan dalam |
| 265 | - | Adding and Editing Properties | 6901 | Menambah properti |
| 266 | - | The |
6942 | Properti |
| 267 | - | Exporting and Importing Properties | 6948 | Mengekspor suatu Copy Pekerjaan Subversion |
| 268 | - | Binary Properties | 6974 | Menambah properti |
| 269 | - | You can configure Subversion and TortoiseSVN to set properties automatically on files and folders when they are added to the repository. There are two ways of doing this. | 6999 | Anda bisa mengkonfigurasi Subversion untuk mengeset properti secara otomatis pada file dan folder ketika mereka ditambahkan ke repositori. Baca |
| 270 | - | TortoiseSVN Project Properties | 7041 | Properti TortoiseSVN |
| 271 | - | project properties | 7047 | Properti Proyek |
| 272 | - | TortoiseSVN properties | 7053 | Properti TortoiseSVN |
| 273 | - | In the Commit dialog you have the option to paste in the list of changed files, including the status of each file (added, modified, etc). |
7087 | Dalam dialog Komit Anda mempunyai opsi untuk melakukan paste dalam daftar file yang diubah, termasuk status dari setiap file (ditambah, diubah, dll). |
| 274 | - | TortoiseSVN can use spell checker modules which are also used by OpenOffice and Mozilla. If you have those installed this property will determine which spell checker to use, i.e. in which language the log messages for your project should be written. |
7093 | TortoiseSVN bisa menggunakan modul pemeriksa ejaan yang juga digunakan oleh OpenOffice dan Mozilla. Jika Anda mempunyai itu terinstalasi, properti ini akan menentukan pemeriksa ejaan yang akan digunakan, contoh dalam bahasa mana pesan log untuk proyek Anda harus ditulis. |
| 275 | - | Some |
7138 | Beberapa properti |
| 276 | - | TortoiseSVN can integrate with some bug tracking tools. This uses project properties that start with |
7144 | TortoiseSVN bisa mengintegrasikan beberapa piranti bugtracking. Penggunaan properti ini, dimulai dengan |
| 277 | - | It can also integrate with some web-based repository browsers, using project properties that start with |
7150 | TortoiseSVN juga dapat berintegrasi dengan beberapa browser repositori berbasis web. Baca |
| 278 | - | Set the project properties on folders | 7156 | Set properti tsvn: pada folder |
| 279 | - | These special project properties must be set on |
7162 | Properti |
| 280 | - | For project properties |
7170 | Untuk properti |
| 281 | - | External Items | 7184 | eksternal |
| 282 | - | Sometimes it is useful to construct a working copy that is made out of a number of different checkouts. For example, you may want different files or subdirectories to come from different locations in a repository, or perhaps from different repositories altogether. If you want every user to have the same layout, you can define the |
7201 | Kadang-kadang adalah berguna untuk membangun copy pekerjaan yang dibuat dalam sejumlah check out berbeda. Sebagai contoh, Anda mungkin menginginkan subdirektori berbeda yang datang dari lokasi yang berbeda dalam repositori, atau barangkali dari repositori yang berbeda sekaligus. Jika Anda ingin setiap pengguna untuk mempunyai tata letak yang sama, Anda bisa mendefinisikan properti |
| 283 | - | External Folders | 7207 | eksternal |
| 284 | - | Let's say you check out a working copy of http://sounds.red-bean.com/repos sounds\n http://graphics.red-bean.com/repos/fast%20graphics \"quick graphs\"\n -r21 http://svn.red-bean.com/repos/skin-maker skins/toolkit\n |
7213 | Katakanlah Anda melakukan check out copy pekerjaan sounds http://sounds.red-bean.com/repos\n quick_graphs http://graphics.red-bean.com/repos/fast%20graphics\n skins/toolkit -r21 http://svn.red-bean.com/repos/skin-maker\n |
| 285 | - | Use explicit revision numbers | 7237 | Angka Revisi Global |
| 286 | - | You should strongly consider using explicit revision numbers in all of your externals definitions, as described above. Doing so means that you get to decide when to pull down a different snapshot of external information, and exactly which snapshot to pull. Besides the common sense aspect of not being surprised by changes to third-party repositories that you might not have any control over, using explicit revision numbers also means that as you backdate your working copy to a previous revision, your externals definitions will also revert to the way they looked in that previous revision, which in turn means that the external working copies will be updated to match they way |
7243 | Anda harus benar-benar mempertimbangkan menggunakan angka revisi eksplisit dalam semua definisi eksternal Anda. Dengan melakukan itu berarti bahwa Anda bisa memutuskan untuk menarik snapshot berbeda dari informasi eksternal, dan memastikan snapshot mana yang ditarik. Disamping supaya Anda tidak dikejutkan oleh perubahan ke repositori pihak ketiga yang mungkin Anda tidak mempunyai kontrol atasnya, menggunakan angka revisi eksternal juga berarti bahwa ketika Anda mengembalikan copy pekerjaan Anda ke revisi sebelumnya, definisi eksternal Anda juga dipulihkan ke cara mereka dikunci dalam revisi sebelumnya itu, yang berarti bahwa copy pekerjaan eksternal akan dimutahirkan untuk menyamai cara |
| 287 | - | Older svn:externals definitions | 7249 | Gunakan svn:externals |
| 288 | - | Relative to repository root | 7294 | Buat Repositori Disini |
| 289 | - | External Files | 7350 | eksternal |
| 290 | - | mark release | 7391 | Merah tua |
| 291 | - | Subversion does not have special commands for branching or tagging, but uses so-called cheap copiesinstead. Cheap copies are similar to hard links in Unix, which means that instead of making a complete copy in the repository, an internal link is created, pointing to a specific tree/revision. As a result branches and tags are very quick to create, and take up almost no extra space in the repository. |
7407 | Subversion tidak mempunyai perintah khusus untuk pencabangan atau pembuatan tag, tapi sebaliknya menggunakan apa-yang-disebut |
| 292 | - | Note that unless you opted to switch your working copy to the newly created branch, creating a Branch or Tag does |
7484 | Catatan bahwa pembuatan Cabang atau Tag |
| 293 | - | Other ways to create a branch or tag | 7490 | Membuat Cabang atau Tag |
| 294 | - | ...that is (not really) the question. While a checkout downloads everything from the desired branch in the repository to your working directory, |
7518 | ...itulah pertanyaannya (yang tidak sebenarnya). Sementara checkout memeriksa apapun dari cabang yang diinginkan ke dalam direktori copy pekerjaan Anda, |
| 295 | - | If you want to work on trunk and branch, but don't want the expense of a fresh checkout, you can use Windows Explorer to make a copy of your trunk checkout in another folder, then |
7544 | Menukar copy pekerjaan Anda ke copy yang baru saja dibuat dalam repositori Anda. Sekali lagi pilih level atas folder dari proyek Anda dan gunakan |
| 296 | - | To be able to work with your freshly generated branch or tag you have several ways to handle it. You can: |
7555 | Agar bisa bekerja dengan copy yang baru Anda mempunyai beberapa cara untuk menanganinya. Anda bisa: |
| 297 | - | Tags are typically used to create a static snapshot of the project at a particular stage. As such they are not normally used for development - that's what branches are for, which is the reason we recommended the |
7561 | Tag biasanya digunakan untuk membuat snapshot statik dari proyek pada tahap tertentu. Karena statik, mereka biasanya tidak digunakan untuk pengembangan - itulah kegunaan cabang, yang menjadi alasan kami merekomendasikan struktur repositori |
| 298 | - | It is important to understand how branching and merging works in Subversion before you start using it, as it can become quite complex. It is highly recommended that you read the chapter |
7600 | Adalah penting untuk mengerti bagaimana mencabangkan dan menggabung pekerjaan dalam Subversion sebelum Anda mulai menggunakannya, karena ini bisa menjadi sedikit rumit. Sangat direkomendasikan bahwa Anda sudah membaca bab |
| 299 | - | There are three common use cases for merging which are handled in slightly different ways, as described below. The first page of the merge wizard asks you to select the method you need. | 7615 | Ada dua penggunaan umum dalam hal menggabungkan yang ditangani dengan cara yang berbeda, seperti dijelaskan dibawah. |
| 300 | - | Merge a range of revisions | 7621 | Menggabungkan Suatu Jangkauan Revisi |
| 301 | - | This method covers the case when you have made a feature branch as discussed in the Subversion book. All trunk changes have been ported to the feature branch, week by week, and now the feature is complete you want to merge it back into the trunk. Because you have kept the feature branch synchronized with the trunk, the latest versions of branch and trunk will be absolutely identical except for your branch changes. | 7641 | Metode ini mencakup hal saat Anda sudah membuat fitur cabang seperti dijelaskan dalam buku Subversion. Semua perubahan trunk sudah dikirimkan ke fitur cabang, minggu demi minggu, dan sekarang fitur menjadi lengkap yang ingin Anda gabung kembali ke trunk. Karena Anda sudah memelihara fitur cabang disinkronisasi dengan trunk, versi terbaru dari cabang dan trunk akan benar-benar sama kecuali untuk perubahan cabang Anda. Maka dalam kasus khusus ini, Anda ingin menggabung dengan membandingkan cabang dengan trunk. |
| 302 | - | Merge two different trees | 7659 | Menggabung Dua Pohon yang Berbeda |
| 303 | - | revision range | 7678 | revisi |
| 304 | - | 7688 | Dalam field |
|
| 305 | - | The easiest way to select the range of revisions you need is to click on |
7718 | Cara termudah untuk memilih jangkauan revisi yang Anda perlukan adalah mengklik |
| 306 | - | If you have already merged some changes from this branch, hopefully you will have made a note of the last revision merged in the log message when you committed the change. In that case, you can use |
7728 | Jika Anda sudah mempunyai gabungan beberapa perubahan dari cabang ini, dengan harapan Anda sudah membuat catatan dari revisi terakhir yang digabung dalam pesan log ketika Anda mengkomit perubahan. Dalam hal itu, Anda bisa menggunakan |
| 307 | - | reintegrate | 7747 | Integrasi Shell |
| 308 | - | In the |
7761 | Dalam field |
| 309 | - | In the |
7788 | Dalam field |
| 310 | - | In the |
7794 | Dalam field |
| 311 | - | You can also use |
7805 | Klik |
| 312 | - | Merge Options | 7811 | piranti merge |
| 313 | - | Most of the time you want merge to take account of the file's history, so that changes relative to a common ancestor are merged. Sometimes you may need to merge files which are perhaps related, but not in your repository. For example you may have imported versions 1 and 2 of a third party library into two separate directories. Although they are logically related, Subversion has no knowledge of this because it only sees the tarballs you imported. If you attempt to merge the difference between these two trees you would see a complete removal followed by a complete add. To make Subversion use only path-based differences rather than history-based differences, check the |
7825 | Biasanya Anda ingin gabungan menjadi perhatian histori file, maka perubahan itu relatif ke asal yang umum digabung. Kadang kala Anda mungkin perlu untuk menggabung file yang mungkin terkait, tapi tidak dalam repositori Anda. Sebagai contoh Anda mungkin telah mengimpor versi 1 dan 2 dari librari pihak ketiga ke dalam direktori terpisah. Meskipun secara logika terkait, Subversion tidak mengetahui ini karena ia hanya melihat tarballs yang Anda impor. Jika Anda mencoba untuk menggabung perbedaan antara dua susunan ini Anda akan melihat penghapusan lengkap diikuti dengan penambahan lengkap. Agar Subversion hanya menggunakan perbedaan berbasis-path daripada perbedaan berbasis-histori, centang kotak |
| 314 | - | Now everything is set up, all you have to do is click on the |
7843 | |
| 315 | - | Reviewing the Merge Results | 7853 | Meninjau Hasil Gabungan |
| 316 | - | For Subversion clients and servers prior to 1.5, no merge information is stored and merged revisions have to be tracked manually. When you have tested the changes and come to commit this revision, your commit log message should |
7863 | Ketika Anda sudah menguji perubahan dan mengkomit revisi ini, pesan log komit Anda akan |
| 317 | - | If you have just merged a feature branch back into the trunk, the trunk now contains all the new feature code, and the branch is obsolete. You can now delete it from the repository if required. | 7878 | Dalam hal ini Anda tidak memerlukan fitur cabang lagi karena fitur baru sekarang terintegrasi ke dalam trunk. Fitur cabang berlebihan dan bisa dihapus dari repositori bila diperlukan. |
| 318 | - | Subversion can't merge a file with a folder and vice versa - only folders to folders and files to files. If you click on a file and open up the merge dialog, then you have to give a path to a file in that dialog. If you select a folder and bring up the dialog, then you must specify a folder URL for the merge. | 7884 | Subversion tidak bisa menggabung file dengan folder dan sebaliknya - hanya folder dengan folder dan file dengan file. Jika Anda mengklik pada file dan membuka dialog gabung, maka Anda hrus memberikan path ke file dalam dialog itu. Jika Anda memilih folder dan muncul dialog, maka Anda harus menetapkan url folder untuk digabung. |
| 319 | - | Merge Tracking | 7890 | Penggabungan |
| 320 | - | merge tracking | 7896 | bugtracking |
| 321 | - | Find out more about merge tracking from Subversion's |
7930 | Download versi terbaru Subversion dari |
| 322 | - | merge conflicts | 7940 | konflik |
| 323 | - | The Merge Conflict Callback Dialog | 7946 | Dialog Penggabungan |
| 324 | - | When a conflict occurs during the merge, you have three ways to handle it. |
7968 | Sekarang Anda harus memilih sumber yang dicopy. Disini Anda mempunyai tiga opsi: |
| 325 | - | merge reintegrate | 7982 | Integrasi Shell |
| 326 | - | The Merge reintegrate Dialog | 7988 | Dialog Penggabungan |
| 327 | - | Your company has always used a locking revision control system in the past and there has been a management decision that locking is best. |
8033 | Perusahaan Anda selalu menggunakan penguncian VCS di masa lalu dan sudah menjadi keputusan manajemen bahwa penguncian adalah yang terbaik. |
| 328 | - | Firstly you need to ensure that your Subversion server is upgraded to at least version 1.2. Earlier versions do not support locking at all. If you are using |
8044 | Pertama Anda perlu memastikan server Subversion Anda dinaikan ke setidaknya versi 1.2. Versi sebelumnya tidak mendukung penguncian sama sekali. Jika Anda menggunakan akses |
| 329 | - | If you select a folder and then use |
8100 | Jika Anda memilih folder dan kemudian menggunakan |
| 330 | - | If you operate a policy where every file has to be locked then you may find it easier to use Subversion's auto-props feature to set the property automatically every time you add new files. Read |
8161 | Jika Anda mengoperasikan aturan dimana setiap file harus dikunci lalu Anda bisa menemukannya lebih mudah untuk menggunakan fitur auto-props Subversion untuk mengeset properti secara otomatis setiap kali Anda menambah file. Baca selengkapnya |
| 331 | - | unified diff | 8202 | Peninjau Unified Diff |
| 332 | - | Patch files are applied to your working copy. This should be done from the same folder level as was used to create the patch. If you are not sure what this is, just look at the first line of the patch file. For example, if the first file being worked on was |
8257 | File patch diterapkan ke copy pekerjaan Anda. Ini harus dikerjakan dari tingkat folder yang sama seperti yang digunakan untuk membuat patch. Jika Anda tidak yakin apa ini, lihat baris pertama dari file patch. Sebagai contoh, jika file pertama bekerja pada |
| 333 | - | From the context menu for that folder, click on All files. If you previously saved a patch to the clipboard, you can use |
8268 | Dari menu konteks untuk folder itu, klik pada |
| 334 | - | When the mouse is over the blame info columns, a context menu is available which helps with comparing revisions and examining history, using the revision number of the line under the mouse as a reference. |
8382 | Jika kursor tetikus di atas kolom-kolom info blame, sebuah menu konteks tersedia untuk menolong membandingkan revisi-revisi dan meneliti sejarah dengan menggunakan nomor revisi dari baris yang di bawah kursor tetikus sebagai suatu referensi. |
| 335 | - | If you want to see the paths involved in the merge, select |
8396 | Dalam copy pekerjaan Anda pilih |
| 336 | - | The settings for TortoiseBlame can be accessed using |
8402 | Memindahkan/Mengcopy satu file bisa dilakukan dengan menggunakan |
| 337 | - | Blame Changes | 8428 | Memulihkan Perubahan |
| 338 | - | Select one revision in the top pane, then pick one file in the bottom pane and select |
8434 | Pilih satu revisi dalam pane atas, lalu ambil satu file dalam pane bawah dan pilih |
| 339 | - | repo-browser | 8461 | repobrowser |
| 340 | - | server viewer | 8472 | repoviewer |
| 341 | - | Save an unversioned copy of the file to your hard drive. | 8491 | buat folder kosong baru pada hard disk Anda |
| 342 | - | Create a new folder in the repository. | 8533 | Item yang ditambahkan ke repositori. |
| 343 | - | Add files or folders directly to the repository. | 8539 | Item yang ditambahkan ke repositori. |
| 344 | - | View/Edit the folder's properties. | 8553 | Properti Folder Khusus |
| 345 | - | Compare the folder with a previously marked folder, either as a unified diff, or as a list of changed files which can then be visually diffed using the default diff tool. This can be particularly useful for comparing two tags, or trunk and branch to see what changed. | 8563 | Jika Anda memilih dua item, Anda bisa melihat perbedaan baik sebagai unified-diff, ataupun sebagai daftar file yang bisa di-diff secara visual menggunakan piranti diff standar. Ini bisa berguna untuk membandingkan dua tag untuk melihat apa yang berubah. |
| 346 | - | If you select two folders in the right pane, you can view the differences either as a unified-diff, or as a list of files which can be visually diffed using the default diff tool. | 8573 | Jika Anda memilih dua item, Anda bisa melihat perbedaan baik sebagai unified-diff, ataupun sebagai daftar file yang bisa di-diff secara visual menggunakan piranti diff standar. Ini bisa berguna untuk membandingkan dua tag untuk melihat apa yang berubah. |
| 347 | - | You can also use the repository browser for drag-and-drop operations. If you drag a folder from explorer into the repo-browser, it will be imported into the repository. Note that if you drag multiple items, they will be imported in separate commits. | 8592 | Anda juga bisa menggunakan browser repositori untuk operasi drag-dan-drop. Jika Anda men-drag folder dari explorer kedalam repo browser, ia akan diimpor ke dalam repositori. Catatan bahwa jika Anda men-drag multipel item, mereka akan diimpor dalam komit yang terpisah. |
| 348 | - | If you want to move an item within the repository, just plussymbol on it, just as it does in Explorer. |
8598 | Jika Anda ingin memindahkan item didalam repositori, cukup plusdidalamnya, seperti halnya Explorer. |
| 349 | - | If you want to copy/move a file or folder to another location and also give it a new name at the same time, you can |
8604 | Jika Anda ingin mengcopy/memindahkan file atau folder ke lokasi lain dan juga memberikan nama baru pada waktu yang sama, Anda bisa |
| 350 | - | Sometimes when you try to open a path you will get an error message in place of the item details. This might happen if you specified an invalid URL, or if you don't have access permission, or if there is some other server problem. If you need to copy this message to include it in an email, just right click on it and use |
8615 | Ada kalanya ketika Anda mencoba untuk membuka path Anda akan mendapatkan pesan kesalahan dari detil item. Ini mungkin terjadi jika Anda menetapkan URL yang tidak benar, atau jika Anda tidak mempunyai perijinan akses, atau jika ada beberapa masalah server lain. Jika Anda perlu untuk mengcopy pesan ini untuk disertakan dalam email, klik kanan padanya dan gunakan |
| 351 | - | revision graph | 8631 | Grafik Revisi |
| 352 | - | In order to generate the graph, TortoiseSVN must fetch all log messages from the repository root. Needless to say this can take several minutes even with a repository of a few thousand revisions, depending on server speed, network bandwidth, etc. If you try this with something like the |
8652 | Agar bisa membuat grafik, TortoiseSVN harus mengambil semua pesan log dari akar repositori. Ini bisa menghabiskan waktu beberapa menit bahkan dengan repositori dari beberapa ribuan revisi, tergantung pada kecepatan server, bandwidth jaringan, dll. Jika Anda mencoba ini dengen sesuatu seperti proyek |
| 353 | - | Revision Graph Nodes | 8662 | Grafik Revisi |
| 354 | - | Deleted items | 8676 | Node dihapus |
| 355 | - | Deleted items eg. a branch which is no longer required, are shown using an octagon (rectangle with corners cut off). The default colour is red. | 8682 | Item-item yang dihapus seperti cabang yang tidak lagi diperlukan, ditampilkan menggunakan oktagon (kotak dengan sudut dipotong). |
| 356 | - | Renamed items | 8688 | ganti nama berkas |
| 357 | - | Working copy revision | 8707 | Melakukan Checkout Copy Pekerjaan |
| 358 | - | Modified working copy | 8717 | copy pekerjaan |
| 359 | - | Normal item | 8727 | File/folder normal |
| 360 | - | Note that by default the graph only shows the points at which items were added, copied or deleted. Showing every revision of a project will generate a very large graph for non-trivial cases. If you really want to see |
8742 | Grafik revisi menampilkan beberapa tipe node: |
| 361 | - | Group branches | 8756 | cabang |
| 362 | - | Show all revisions | 8802 | Tampilkan revisi-revisi HEAD |
| 363 | - | Show WC revision | 8853 | Tampilkan revisi-revisi HEAD |
| 364 | - | Show WC modifications | 8863 | modifikasi |
| 365 | - | Filter | 8873 | filter |
| 366 | - | Sometimes the revision graph contains more revisions than you want to see. This option opens a dialog which allows you to restrict the range of revisions displayed, and to hide particular paths by name. | 8878 | Terkadang grafik revisi terlalu rinci dibandingkan dengan apa yang Anda butuhkan. |
| 367 | - | Using the Graph | 8904 | Grafik Revisi |
| 368 | - | If you select two revisions (Use |
8919 | Jika Anda memilih dua revisi (Gunakan |
| 369 | - | Learn to Read the Revision Graph | 8939 | Grafik Revisi |
| 370 | - | unversioned 'working copy' | 8999 | Gunakan copy pekerjaan berulang |
| 371 | - | Exporting single files | 9039 | Properti Subversion |
| 372 | - | Exporting a Change Tree | 9053 | Properti Subversion |
| 373 | - | Removing a working copy from version control | 9063 | Menghapus file dalam |
| 374 | - | repository URL changed | 9098 | URL Repositori |
| 375 | - | server moved | 9104 | hilangkan |
| 376 | - | moved server | 9110 | server proxy |
| 377 | - | 9121 | ||
| 378 | - | Integration with Bug Tracking Systems / Issue Trackers | 9171 | Integrasi dengan Sistem Bugtracking / Pelacak Isu |
| 379 | - | bug tracking | 9177 | bugtracking |
| 380 | - | bug tracker | 9183 | pelacakbug |
| 381 | - | issue tracker | 9190 | pelacakisu |
| 382 | - | Adding Issue Numbers to Log Messages | 9226 | Jumlah pesan log bawaan |
| 383 | - | You can integrate a bug tracking tool of your choice in TortoiseSVN. To do this, you have to define some properties, which start with |
9232 | Anda bisa mengintegrasikan Piranti Bugtracking pilihan Anda dalam TortoiseSVN. Untuk melakukan ini, Anda harus mendefinisikan beberapa properti, yang dimulai dengan |
| 384 | - | Set this property to the URL of your bug tracking tool. It must be properly URI encoded and it has to contain |
9238 | Set properti ini ke url dari piranti bugtracking Anda. Ini harus dikode-URI-kan dengan benar dan harus berisi |
| 385 | - | Set this to |
9256 | Set ini menjadi |
| 386 | - | There are two ways to integrate TortoiseSVN with issue trackers. One is based on simple strings, the other is based on |
9262 | Ada dua cara untuk mengintegrasikan TortoiseSVN dengan pelacak isu. Pertama berdasarkan string sederhana, kedua berdasarkan |
| 387 | - | This property activates the bug tracking system in |
9272 | |
| 388 | - | This text is shown by TortoiseSVN on the commit dialog to label the edit box where you enter the issue number. If it's not set, |
9283 | Teks ini ditampilkan oleh TortoiseSVN pada dialog komit ke label kotak edit dimana Anda memasukan issuenumber. Jika tidak di-set, |
| 389 | - | If set to |
9289 | Jika di-set ke |
| 390 | - | This property activates the bug tracking system in |
9304 | |
| 391 | - | If you want to catch bug IDs as used in the expression above inside a log message, you could use the following regex strings, which are the ones used by the TortoiseSVN project: |
9314 | Jika Anda ingin menangkap setiap pola \"issue #XXX\" dan \"issue #890, #789\" di dalam suatu log pesan, Anda bisa menggunakan string regex berikut: |
| 392 | - | If only one expression is set, then the bare bug IDs must be matched in the groups of the regex string. Example: |
9328 | Jika hanya satu ekspresi yang di-set, maka bug ID harus sama dengan yang ada dalam grup dari srting regex. Contoh: |
| 393 | - | If you are unfamiliar with regular expressions, take a look at the introduction at |
9334 | Jika Anda tidak terbiasa dengan ekspresi reguler, lihat dokumentasi online dan tutorial di |
| 394 | - | In the approach with |
9340 | Dalam pendekatan dengan |
| 395 | - | These properties must be set on folders for the system to work. When you commit a file or folder the properties are read from that folder. If the properties are not found there, TortoiseSVN will search upwards through the folder tree to find them until it comes to an unversioned folder, or the tree root (eg. |
9367 | Properti ini harus di-set pada folder agar sistem bekerja. Ketika Anda komit file atau folder, properti dibaca dari folder itu. Jika properti tidak ditemukan disana, TortoiseSVN akan mencari diatasnya melalui susunan folder untuk menemukannya sampai ke folder tidak berversi, atau akar susunan (contoh. |
| 396 | - | This issue tracker integration is not restricted to TortoiseSVN; it can be used with any Subversion client. For more information, read the full |
9381 | Integrasi pelacak isu ini tidak terbatas pada TortoiseSVN; ia bisa digunakan dengan setiap klien Subversion. Untuk informasi lebih jauh, baca |
| 397 | - | web view | 9410 | webview |
| 398 | - | repo viewer | 9416 | repoviewer |
| 399 | - | You can integrate a repo viewer of your choice in TortoiseSVN. To do this, you have to define some properties which define the linkage. They must be set on Folders: ( |
9435 | Anda dapat menggabungkan suatu pelihat repo kesukaan Anda dalam TortoiseSVN. Untuk melakukannya, Anda harus menentukan beberapa properti yang menentukan hubungannya. Mereka harus diatur pada Folder ( |
| 400 | - | Set this property to the URL of your repo viewer to view all changes in a specific revision. It must be properly URI encoded and it has to contain |
9440 | Atur properti ini ke url dari pelihatrepo untuk melihat semua perubahan dalam suatu revisi spesifik. Ini harus dienkode URI secara benar dan harus mengandung |
| 401 | - | Set this property to the URL of your repo viewer to view changes to a specific file in a specific revision. It must be properly URI encoded and it has to contain |
9445 | Atur properti ini ke url dari pelihatrepo Anda untuk melihat perubahan-perubahan dari suatu file spesifik dalam suatu revisi spesifik. Url itu harus dienkode URI dengan benar dan harus mengandung |
| 402 | - | No Repo Viewer Links from Repository Browser | 9455 | Browser Repositori |
| 403 | - | Global ignore patterns are used to prevent unversioned files from showing up e.g. in the commit dialog. Files matching the patterns are also ignored by an import. Ignore files or directories by typing in the names or extensions. Patterns are separated by spaces e.g. |
9560 | Pola abaikan global digunakan untuk menjaga file tidak berversi muncul contoh dalam dialog komit. File yang cocok dengan pola juga diabaikan oleh impor. Abaikan file atau direktori dengan mengetikkan nama atau ekstensi. Pola dipisahkan dengan spasi contoh. |
| 404 | - | Set file dates to the last commit time |
9581 | Set tanggal file ke \"waktu komit terakhir\" |
| 405 | - | This option tells TortoiseSVN to set the file dates to the last commit time when doing a checkout or an update. Otherwise TortoiseSVN will use the current date. If you are developing software it is generally best to use the current date because build systems normally look at the date stamps to decide which files need compiling. If you use last commit timeand revert to an older file revision, your project may not compile as you expect it to. |
9587 | Opsi ini memberitahu TortoiseSVN untuk mengeset tanggal file ke waktu komit terakhir saat melakukan checkout atau pemutahiran. Sebaliknya TortoiseSVN akan menggunakan tanggal saat ini. Jika Anda mengembangkan software biasanya cara terbaik untuk menggunakan tanggal saat ini karena sistem pembuatan umumnya melihat ke cap tanggal untuk memutuskan file mana yang perlu dikompilasi. Jika Anda menggunakan \"waktu komit terakhir\" dan memulihkan ke revisi file lebih lama, proyek Anda mungkin tidak dikompilasi seperti yang Anda harapkan. |
| 406 | - | Use |
9598 | Gunakan |
| 407 | - | Use |
9604 | Gunakan direktori \"_svn\" daripada \".svn\" |
| 408 | - | Context Menu Settings | 9625 | Menu Konteks |
| 409 | - | The Settings Dialog, Context Menu Page | 9631 | HDialog Seting, Halaman Set Ikon |
| 410 | - | Limits the number of log messages that TortoiseSVN fetches when you first select |
9670 | Batasi jumlah pesan log yang diambil TortoiseSVN saat pertama Anda memilih |
| 411 | - | Use URL of WC as the default From:URL |
9742 | Gunakan URL WC sebagai URL \"Dari:\" bawaan |
| 412 | - | Use auto-completion of file paths and keywords | 9793 | Gunakan otomatis pelengkapan dari path file dan kata kunci |
| 413 | - | The commit dialog includes a facility to parse the list of filenames being committed. When you type the first 3 letters of an item in the list, the auto-completion box pops up, and you can press Enter to complete the filename. Check the box to enable this feature. | 9799 | Dialog komit menyertakan fasilitas untuk mengurai daftar nama file yang sedang dikomit. Bila Anda mengetikan 3 huruf pertama dari item dalam daftar, kotak otomatis pelengkapan muncul, dan Anda bisa menekan Enter untuk melengkapi nama file. Centang kotak untuk menghidupkan fitur ini. |
| 414 | - | Timeout in seconds to stop the auto-completion parsing | 9805 | Waktu habis dalam detik untuk menghentikan penguraian otomatis pelengkapan |
| 415 | - | The auto-completion parser can be quite slow if there are a lot of large files to check. This timeout stops the commit dialog being held up for too long. If you are missing important auto-completion information, you can extend the timeout. | 9811 | Pengurai otomatis pelengkapan bisa agak lambat jika banyak file besar untuk diperiksa. Waktu habis ini menghentikan dialog komit untuk menampung terlalu lama. Jika Anda kehilangan informasi otomatis pelengkapan penting, Anda bisa memperbesar waktu habis. |
| 416 | - | Only use spellchecker when |
9817 | Hanya gunakan pemeriksa ejaan saat tsvn:projectlanguage di-set |
| 417 | - | When you type in a log message in the commit dialog, TortoiseSVN stores it for possible re-use later. By default it will keep the last 25 log messages for each repository, but you can customize that number here. If you have many different repositories, you may wish to reduce this to avoid filling your registry. | 9833 | TortoiseSVN menyimpan setidaknya 25 pesan log yang Anda masukan untuk setiap repositori. Anda bisa mengkustomisasi jumlah yang disimpan disini. Jika Anda mempunyai banyak repositori berbeda, Anda mungkin ingin mengurangi ini untuk menghindari pengisian registri Anda. |
| 418 | - | Re-open commit and branch/tag dialog after a commit failed | 9843 | Buka-lagi dialog komit setelah komit gagal |
| 419 | - | Select items automatically | 9854 | Urut item secara numerik |
| 420 | - | Revision Graph Settings | 10000 | Grafik Revisi |
| 421 | - | The Settings Dialog, Revision Graph Page | 10006 | Dialog Seting, Halaman Umum |
| 422 | - | Modify Colors | 10024 | piranti diff |
| 423 | - | Revision Graph Colors | 10034 | Grafik Revisi |
| 424 | - | The Settings Dialog, Revision Graph Colors Page | 10040 | Dialog Seting, Halaman Warna |
| 425 | - | Deleted Node | 10050 | Node dihapus |
| 426 | - | Added Node | 10060 | Node ditambah |
| 427 | - | Renamed Node | 10070 | Node diganti nama |
| 428 | - | Modified Node | 10080 | Diubah / dicopy |
| 429 | - | Unchanged Node | 10090 | Tidak berubah, dan saat ini |
| 430 | - | HEAD node | 10100 | Node ditambah |
| 431 | - | Current HEAD revision in the repository. | 10106 | Revisi HEAD dalam repositori |
| 432 | - | Selected Node Markers | 10152 | Node dihapus |
| 433 | - | The Settings Dialog, Icon Overlays Page | 10175 | HDialog Seting, Halaman Set Ikon |
| 434 | - | 10181 | ||
| 435 | - | By default, overlay icons and context menus will appear in all open/save dialogs as well as in Windows Explorer. If you want them to appear |
10187 | Standarnya, lapisan ikon akan muncul dalam semua dialog buka/simpan juga dalam Windows Explorer. Jika Anda menginginkan |
| 436 | - | You can also choose to mark folders as modified if they contain unversioned items. This could be useful for reminding you that you have created new files which are not yet versioned. This option is only available when you use the |
10197 | Jika Anda memilih opsi standar, Anda juga bisa memilih untuk menandai folder sebagai diubah jika mereka berisi item-item tidak berversi. Ini bisa berguna untuk mengingatkan Anda bahwa Anda sudah membuat file baru yang belum diberi versi. |
| 437 | - | Caches all status information in a separate process ( |
10208 | Cache semua informasi status dalam proses terpisah ( |
| 438 | - | Advantage: the overlays show the status recursively, i.e. if a file deep inside a working copy is modified, all folders up to the working copy root will also show the modified overlay. And since the process can send notifications to the shell, the overlays on the left tree view usually change too. | 10214 | Keuntungan: lapisan menampilkan status secara rekursif, contoh. jika kedalaman file di dalam copy pekerjaan diubah, semua folder sampai akar copy pekerjaan akan juga menampilkan lapisan yang diubah. Dan karena proses bisa mengirimkan pemberitahuan ke shell, lapisan pada treeview kiri biasanya berubah juga. |
| 439 | - | Advantage: needs only very little memory (around 1 MB of RAM) and can show the status in |
10235 | Keuntungan: hanya memerlukan sedikit memori (sekirar 1 MB dari RAM) dan bisa menampilkan status secara |
| 440 | - | Disadvantage: Status information of files and folders is not shown in Explorer. To see if your working copies are modified, you have to use the Check for modificationsdialog. |
10261 | Kerugian: Informasi status dari file dan folder yang ditampilkan dalam Explorer. Untuk melihat copy pekerjaan Anda dimodifikasi, Anda harus menggunakan dialog \"Periksa modifikasi\". |
| 441 | - | Since it takes quite a while to fetch the status of a working copy, TortoiseSVN uses a cache to store the status so the explorer doesn't get hogged too much when showing the overlays. You can choose which type of cache TortoiseSVN should use according to your system and working copy size here: |
10267 | Karena ini memerlukan waktu tidak sedikit untuk mengambil status dari copy pekerjaan, TortoiseSVN menggunakan cache untuk menyimpan status agar explorer tidak berputar-putar terlalu lama ketika menampilkan lapisan. Anda bisa memilih tipe dari cache yang harus digunakan TortoiseSVN tergantung pada sistem Anda dan ukuran copy pekerjaan disini: |
| 442 | - | The next group allows you to select which classes of storage should show overlays. By default, only hard drives are selected. You can even disable all icon overlays, but where's the fun in that? | 10273 | |
| 443 | - | If you need to set up per-repository proxy settings, you will need to use the Subversion |
10385 | Disini Anda perlu menyiapkan seting proxy per-repositori, Anda akan perlu untuk menggunakan file |
| 444 | - | For example, with ExamDiff Pro: C:\\Path-To\\ExamDiff.exe %base %mine --left_display_name:%bname\n --right_display_name:%yname\n C:\\Path-To\\kdiff3.exe %base %mine --L1 %bname --L2 %yname\n C:\\Path-To\\WinMerge.exe -e -ub -dl %bname -dr %yname %base %mine\n C:\\Path-To\\compare.exe /max /wait /title1:%bname /title2:%yname\n %base %mine\n C:\\Path-To\\uc.exe %base %mine -title1 %bname -title2 %yname\n |
10477 | Sebagai contoh, dengan ExamDiff Pro: C:\\Path-To\\ExamDiff.exe %base %mine\n C:\\Path-To\\kdiff3.exe %base %mine --L1 %bname --L2 %yname\n C:\\Path-To\\WinMerge.exe -e -ub -dl %bname -dr %yname %base %mine\n C:\\Path-To\\compare.exe /max /wait /title1:%bname /title2:%yname\n %base %mine\n |
| 445 | - | If you use the |
10506 | Jika Anda menggunakan properti |
| 446 | - | If you have configured an alternate diff tool, you can access TortoiseMerge |
10516 | Dari menu konteks pada dialog Anda bisa menampilkan diff dari perubahan. Periksalah perubahan lokal yang sudah |
| 447 | - | For example, with Perforce Merge: C:\\Path-To\\P4Merge.exe %base %theirs %mine %merged\n C:\\Path-To\\kdiff3.exe %base %mine %theirs -o %merged\n --L1 %bname --L2 %yname --L3 %tname\n C:\\Path-To\\compare.exe /max /wait /3 /title1:%tname /title2:%bname\n /title3:%yname %theirs %base %mine %merged /a2\n C:\\Path-To\\WinMerge.exe %merged\n |
10562 | Sebagai contoh, dengan Perforce Merge: C:\\Path-To\\P4Merge.exe %base %theirs %mine %merged\n C:\\Path-To\\kdiff3.exe %base %mine %theirs -o %merged\n --L1 %bname --L2 %yname --L3 %tname\n C:\\Path-To\\compare.exe /max /wait /3 /title1:%tname /title2:%bname\n /title3:%yname %theirs %base %mine %merged /a2\n |
| 448 | - | DiffProgram for |
10598 | Diffuntuk file .jpg :-) Anda juga dapat mengasosiasikan properti |
| 449 | - | To associate using a file extension, you need to specify the extension. Use |
10604 | Untuk mengasosiasi dengan menggunakan suatu ekstensi file, Anda perlu untuk menetapkan ekstensinya saja, dengan didahului titik dan tidak dengan spek wildcard. Gunakan |
| 450 | - | If you want to remove a single item from one of the combo boxes you can do that in-place. Just click on the arrow to drop the combo box down, move the mouse over the item you want to remove and type |
10649 | Jika Anda ingin mencopot suatu item tunggal dari salah satu kotak kombo, Anda dapat melakukannya di tempat. Cukup klik pada anak panah untuk menjatuhkan kotak kombo ke bawah, geser tetikus di atas item yang Anda inginkan supaya dicopot dan ketik |
| 451 | - | If you want to clear authentication data for one particular server only, read |
10693 | Jika Anda ingin membersihkan data auth hanya untuk server tertentu, baca |
| 452 | - | log cache | 10721 | log pesan |
| 453 | - | The Settings Dialog, Log Cache Page | 10727 | HDialog Seting, Halaman Set Ikon |
| 454 | - | If the repository cannot be contacted | 10765 | Hubungi repositori saat mulai |
| 455 | - | Cached Repositories | 10811 | Repositori |
| 456 | - | Log Cache Statistics | 10833 | statistik |
| 457 | - | The Settings Dialog, Log Cache Statistics | 10839 | Dialog Seting, Halaman Tampilan dan Rasa |
| 458 | - | Connection | 10861 | Konfigurasi |
| 459 | - | Last update | 10871 | Pos-mutahirkan |
| 460 | - | The last time the cache content was changed. | 10877 | Alamat IP server sudah berubah. |
| 461 | - | Authors | 10891 | Otorisasi |
| 462 | - | Paths | 10901 | Patch |
| 463 | - | Max revision | 10919 | revisi |
| 464 | - | Revision count | 10929 | Revisi |
| 465 | - | Client Side Hook Scripts | 10943 | Naskah Hook |
| 466 | - | 10958 | ||
| 467 | - | Called before the commit dialog is shown. You might want to use this if the hook modifies a versioned file and affects the list of files that need to be committed and/or commit message. However you should note that because the hook is called at an early stage, the full list of objects selected for commit is not available. | 10986 | Dipanggil sebelum dialog komit ditampilkan. Anda mungkin ingin untuk menggunakan ini jika hook mengubah suatu file berversi dan mempengaruhi daftar file yang perlu dikomit. |
| 468 | - | Called after the user clicks |
10997 | Dipanggil setelah pengguna mengeklik |
| 469 | - | The command line includes several parameters which get filled in by TortoiseSVN. The parameters passed depend upon which hook is called. Each hook has its own parameters which are passed in the following order: |
11054 | Baris perintah dapat mengandung beberapa parameter yang akan diisi oleh TortoiseSVN. Ketersediaan parameter-parameter tersebut tergantung pada hook mana yang dipanggil. |
| 470 | - | Possible values are: |
11092 | Membuat repositori dalam |
| 471 | - | The repository revision to which the update should be done or after a commit completes. | 11101 | Revisi repositori setelah suatu komit selesai. |
| 472 | - | The meaning of each of these parameters is described here: |
11114 | Arti dari tiap variabel-variabel berikut dijelaskan di sini: |
| 473 | - | Normally you will want to hide ugly DOS boxes when the script runs, so |
11127 | Lazimnya Anda akan ingin untuk menyembunyikan kotak-kotak DOS yang jelek saat naskah-naskah dijalankan, jadi |
| 474 | - | The Settings Dialog, Issue Tracker Integration Page | 11145 | Dialog Seting, Halaman Umum |
| 475 | - | TortoiseBlame Settings | 11167 | Seting TortoiseSVN |
| 476 | - | The Settings Dialog, TortoiseBlame Page | 11173 | Dialog Seting, Halaman Warna |
| 477 | - | A few infrequently used settings are available only by editing the registry directly. It goes without saying that you should only edit registry values if you know what you are doing. | 11217 | Beberapa seting yang jarang digunakan tersedia hanya dengan mengedit registri secara langsung. |
| 478 | - | Cache tray icon | 11228 | Cache Ikon Tray |
| 479 | - | Context Menu Icons | 11247 | Menu Konteks |
| 480 | - | Block Overlay Status | 11257 | Seting Lapisan Ikon |
| 481 | - | Update Check URL | 11266 | URL checkout bawaan |
| 482 | - | Explorer columns everywhere | 11284 | Kolom Explorer |
| 483 | - | VS.NET 2003 when used with web projects can't handle the |
11341 | VS.NET ketika digunakan dengan proyek web tidak bisa menangani folder |
| 484 | - | As of Version 1.3.0 of Subversion and TortoiseSVN, you can set the environment variable |
11351 | Sejak Versi 1.3.0 dari Subversion dan TortoiseSVN, Anda bisa mengeset variabel lingkungan |
| 485 | - | For more information, and other ways to avoid this problem in the first place, check out the article about this in our |
11357 | Untuk informasi lebih jauh, dan cara lain untuk menghindari masalah ini, periksa artikel mengenai ini dalam |
| 486 | - | While working on TortoiseSVN we love to listen to music. And since we spend many hours on the project we need a |
11377 | Ketika bekerja pada TortoiseSVN kami senang mendengarkan musik. Dan karena kami meluangkan banyak jam pada proyek kami memerlukan |
| 487 | - | version number in files | 11402 | File konfigurasi Subversion |
| 488 | - | If this switch is given, SubWCRev will exit with |
11471 | Jika saklar ini diberikan, SubWCRev akan keluar dengan ERRORLEVEL 7 jika copy pekerjaan berisi modifikasi lokal. Ini bisa digunakan untuk menjaga pembangunan dengan perubahan yang ada tidak dikomit. |
| 489 | - | If this switch is given, SubWCRev will exit with |
11481 | Jika saklar ini diberikan, SubWCRev akan keluar dengan ERRORLEVEL 8 jika copy pekerjaan berisi revisi campuran. Ini bisa digunakan untuk mencegah pembangunan dengan copy pekerjaan yang dimutahirkan sebagian. |
| 490 | - | If this switch is given, SubWCRev will exit with |
11491 | Jika saklar ini diberikan, SubWCRev akan keluar dengan ERRORLEVEL 9 jika file tujuan sudah ada. |
| 491 | - | svn:externals | 11502 | Gunakan svn:externals |
| 492 | - | If this switch is given, SubWCRev will examine directories which are included with |
11508 | Jika saklar ini diberikan, SubWCRev akan memeriksa direktori yang disertakan dengan svn:externals, tapi hanya jika mereka dari repositori yang sama. Tindakan standarnya adalah mengabaikan eksternal. |
| 493 | - | If this switch is given, SubWCRev will output the revision numbers in HEX. | 11514 | Jika saklar ini diberikan, SubWCRev akan keluar dengan ERRORLEVEL 9 jika file tujuan sudah ada. |
| 494 | - | If this switch is given, SubWCRev will output the revision numbers in HEX, with '0X' prepended. | 11520 | Jika saklar ini diberikan, SubWCRev akan keluar dengan ERRORLEVEL 9 jika file tujuan sudah ada. |
| 495 | - | online reference | 11559 | Perbedaan File |
| 496 | - | Replaced with the current system date/time. This can be used to indicate the build time. Time formatting can be used as described for |
11576 | Diganti dengan tanggal/jam sistem saat ini. Ini bisa digunakan untuk menunjukan waktu pembangunan. Format internasional digunakan seperti dijelaskan di atas. |
| 497 | - | 11608 | Diganti dengan TText jika ada revisi pemutahiran campuran, atau FText jika tidak. | |
| 498 | - | 11619 | Diganti dengan TText jika ada modifikasi lokal, atau FText jika tidak. | |
| 499 | - | $WCINSVN?TText:FText$ | 11630 | $WCMODS?TText:FText$ |
| 500 | - | $WCNEEDSLOCK?TText:FText$ | 11640 | $WCMODS?TText:FText$ |
| 501 | - | 11651 | Diganti dengan TText jika ada modifikasi lokal, atau FText jika tidak. | |
| 502 | - | $WCISLOCKED?TText:FText$ | 11657 | $WCMIXED?TText:FText$ |
| 503 | - | Replaced with the name of the lock owner. | 11671 | Diganti dengan revisi komit tertinggi dalam copy pekerjaan. |
| 504 | - | Replaced with the comment of the lock. | 11677 | Diganti dengan revisi komit tertinggi dalam copy pekerjaan. |
| 505 | - | \n // Test file for SubWCRev: testfile.tmpl\n \n char *Revision = \"$WCREV$\";\n char *Modified = \"$WCMODS?Modified:Not modified$\";\n char *Date = \"$WCDATE$\";\n char *Range = \"$WCRANGE$\";\n char *Mixed = \"$WCMIXED?Mixed revision WC:Not mixed$\";\n char *URL = \"$WCURL$\";\n \n #if $WCMODS?1:0$\n #error Source is modified\n #endif\n \n // End of file\n |
11702 | \n // Test file untuk SubWCRev\n \n char *Revision = \"$WCREV$\";\n char *Modified = \"$WCMODS?Modified:Not modified$\";\n char *Date = \"$WCDATE$\";\n char *RevRange = \"$WCRANGE$\";\n char *Mixed = \"$WCMIXED?Mixed revision WC:Not mixed$\";\n char *URL = \"$WCURL$\";\n \n #if $WCMODS?1:0$\n #error Source Modified\n #endif\n \n // EndOfFile\n |
| 506 | - | \n // Test file for SubWCRev: testfile.txt\n \n char *Revision = \"3701\";\n char *Modified = \"Modified\";\n char *Date = \"2005/06/15 11:15:12\";\n char *Range = \"3699:3701\";\n char *Mixed = \"Mixed revision WC\";\n char *URL = \"http://project.domain.org/svn/trunk/src\";\n \n #if 1\n #error Source is modified\n #endif\n \n // End of file\n |
11742 | \n // Test file untuk SubWCRev\n \n char *Revision = \"3701\";\n char *Modified = \"Modified\";\n char *Date = \"2005/06/15 11:15:12\";\n char *RevRange = \"3699:3701\";\n char *Mixed = \"Mixed revision WC\";\n char *URL = \"http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/src/SubWCRev\";\n \n #if 1\n #error Source Modified\n #endif\n \n // EndOfFile\n |
| 507 | - | Method | 11794 | Metode Akses |
| 508 | - | The highest commit revision in the working copy. Equivalent to |
11819 | Diganti dengan revisi komit tertinggi dalam copy pekerjaan. |
| 509 | - | The commit date/time of the highest commit revision. Equivalent to |
11825 | Diganti dengan tanggal/jam komit dari revisi komit tertinggi. Untuk menghindari kebingunan, format internasional digunakan, contoh |
| 510 | - | The author of the highest commit revision, that is, the last person to commit changes to the working copy. | 11831 | Diganti dengan revisi komit tertinggi dalam copy pekerjaan. |
| 511 | - | The minimum update revision, as shown in |
11843 | Menampilkan grafik revisi untuk path yang diberikan dalam |
| 512 | - | The maximum update revision, as shown in |
11849 | Menampilkan grafik revisi untuk path yang diberikan dalam |
| 513 | - | True if there are local modifications | 11855 | Diganti dengan TText jika ada modifikasi lokal, atau FText jika tidak. |
| 514 | - | Replaced with the repository URL of the working copy path used in |
11870 | Diganti dengan URL repositori path copy pekerjaan dioper ke SubWCRev. |
| 515 | - | True if the item has the |
11880 | Menambah file dalam |
| 516 | - | Because TortoiseSVN is being developed all the time it is sometimes hard to keep the documentation completely up to date. We maintain an |
12310 | Karena TortoiseSVN sedang dikembangkan terus menerus ada kalanya sulit untuk memelihara dokumentasi sepenuhnya mutahir. Kami memelihara |
| 517 | - | We also maintain a project |
12316 | Kami juga memelihara |
| 518 | - | The recommended way is by |
12355 | Cara yang direkomendasikan adalah dengan |
| 519 | - | commit message | 12371 | Pesan Log Komit |
| 520 | - | empty message | 12377 | log pesan |
| 521 | - | In the repository folder on the server, there's a sub-folder |
12398 | Dalam folder repositori pada server, ada subfolder |
| 522 | - | Roll back (Undo) revisions in the repository | 12444 | Gulung kembali revisi dalam repositori |
| 523 | - | undo commit | 12455 | komit |
| 524 | - | undo change | 12461 | Memulihkan Perubahan |
| 525 | - | Select |
12482 | Pilih |
| 526 | - | Select the revision you wish to revert. If you want to undo a range of revisions, select the first one and hold the |
12488 | Pilih revisi yang ingin Anda pulihkan. Jika Anda ingin membatalkan sederetan revisi, pilih yang pertama dan tekan tombol shift sementara memilih yang terakhir. Catatan bahwa untuk multipel revisi, deretan harus tidak terpisah dengan tanpa jarak. |
| 527 | - | Or if you want to make an earlier revision the new HEAD revision, |
12494 | Atau jika Anda ingin membuat revisi sebelumnya untuk revisi HEAD baru, |
| 528 | - | In the |
12521 | Dalam field |
| 529 | - | In the |
12537 | Dalam field |
| 530 | - | Use |
12548 | Gunakan svndumpfilter |
| 531 | - | The only way to remove data from the repository is to use the Subversion command line tool |
12559 | Satu-satunya cara untuk menghapus data dari repositori adalah menggunakan piranti baris perintah Subversion |
| 532 | - | Compare two revisions of a file or folder | 12565 | Bandingkan dua revisi file |
| 533 | - | compare folders | 12576 | bandingkan file |
| 534 | - | If you want to compare two revisions in an item's history, for example revisions 100 and 200 of the same file, just use |
12587 | Jika Anda ingin membandingkan dua revisi dalam histori file, misalnya revisi 100 dan 200 dari file yang smaa, cukup gunakan |
| 535 | - | If you want to compare the same item in two different trees, for example the trunk and a branch, you can use the repository browser to open up both trees, select the file in both places, then use |
12593 | Jika Anda ingin membandingkan file yang sama dalam susunan yang berbeda, misalnya trunk dan cabang, Anda bisa menggunakan browser repositori untuk membuka kedua susunan, pilih file dalam kedua tempat lalu gunakan |
| 536 | - | If you want to compare two trees to see what has changed, for example the trunk and a tagged release, you can use |
12599 | Jika Anda ingin membandingkan dua susunan untuk melihat apa yang berubah misalnya trunk dan rilis tag, Anda bisa menggunakan |
| 537 | - | vendor projects | 12615 | Indeks proyek |
| 538 | - | Set the |
12631 | Set properti |
| 539 | - | Commit the new folder. Now when you update, Subversion will pull a copy of that project from its repository into your working copy. The sub-folders will be created automatically if required. Each time you update your main working copy, you will also receive the latest version of all external projects. | 12637 | Komit folder baru. Sekarang ketika Anda memutahirkan, Subversion akan menarik copy proyek itu dari repositorinya ke dalam copy pekerjaan Anda. Subfolder akan diperlakukan otomatis jika diperlukan. Setiap kali Anda memutahirkan copy pekerjaan utama Anda, Anda juga akan menerima versi terbaru dari semua proyek eksternal. |
| 540 | - | If you frequently need to open the repository browser at a particular location, you can create a desktop shortcut using the automation interface to TortoiseProc. Just create a new shortcut and set the target to: TortoiseProc.exe /command:repobrowser /path:\"url/to/repository\"\n |
12719 | Jika Anda sering membuka browser repositori di lokasi tertentu, Anda bisa membuat jalan pintas desktop menggunakan interface otomatis ke TortoiseProc. Cukup buat jalan pintas baru dan set sasaran ke: TortoiseProc.exe /command:repobrowser /path:\"url/ke/repository\" /notempfile\n |
| 541 | - | remove versioning | 12736 | Pembuatan versi direktori |
| 542 | - | detach from repository | 12742 | repositori |
| 543 | - | Hold the |
12758 | |
| 544 | - | 12764 | ||
| 545 | - | Add the file/folder to the ignore list so you don't get into the same trouble again. | 12770 | Tambah folder ke daftar abaikan agar Anda tidak mendapat masalah yang sama lagi. |
| 546 | - | Unversion a working copy | 12781 | Merelokasi copy pekerjaan |
| 547 | - | If you have a working copy which you want to convert back to a plain folder tree without the |
12787 | Ada kalanya Anda ingin membuat copy lokal tanpa direktori |
| 548 | - | Remove a working copy | 12793 | Merelokasi copy pekerjaan |
| 549 | - | domain controller | 12834 | domaincontroller |
| 550 | - | The TortoiseSVN installer comes as an MSI file, which means you should have no problems adding that MSI file to the group policies of your domain controller. | 12844 | Instalator TortoiseSVN datang sebagai file msi, yang berarti Anda seharusnya tidak mempunyai masalah menambahkan file msi itu ke aturan grup dari kontroler domain Anda. |
| 551 | - | A good walk-through on how to do that can be found in the knowledge base article 314934 from Microsoft: |
12850 | Langkah-langkah yang baik bagaimana melakukan itu bisa ditemukan dalam artikel basis pengetahuan 314934 dari Microsoft: |
| 552 | - | Versions 1.3.0 and later of TortoiseSVN must be installed under |
12856 | Versi 1.3.0 dan berikutnya dari TortoiseSVN harus diinstalasi di bawah |
| 553 | - | Versions 1.4.0 and later of TortoiseSVN allow you to redirect that upgrade check to your intranet server. You can set the registry key 1.4.1.6000\n A new version of TortoiseSVN is available for you to download!\n http://192.168.2.1/downloads/TortoiseSVN-1.4.1.6000-svn-1.4.0.msi\n |
12897 | Versi 1.4.0 dan selanjutnya dari TortoiseSVN membolehkan Anda untuk mengalihkan pemeriksaan pemutahiran itu ke server intranet Anda. Anda bisa men-set kunci registri Anda 1.4.1.6000\n Versi TortoiseSVN baru tersedia bagi Anda untuk di download!\n http://192.168.2.1/downloads/TortoiseSVN-1.4.1.6000-svn-1.4.0.msi\n |
| 554 | - | As of version 1.4.0 and later, the TortoiseSVN installer doesn't provide the user with the option to set the |
12932 | Sejak versi 1.4.0 dan selanjutnya, instalator TortoiseSVN tidak menyediakan opsi bagi pengguna untuk men-set variabel lingkungan SVN_ASP_DOT_NET_HACK lagi, karena menyebabkan banyak masalah dan membingungkan bagi pengguna yang selalu menginstalasi |
| 555 | - | But that option is only hidden for the user. You still can force the TortoiseSVN installer to set that environment variable by setting the msiexec /i TortoiseSVN-1.4.0.msi ASPDOTNETHACK=TRUE\n |
12938 | Tapi opsi itu hanya tersembunyi bagi pengguna. Anda masih bisas memaksa instalator TortoiseSVN untuk men-set variabel lingkungan itu dengan menyeting properti ASPDOTNETHACK ke TRUE. Sebagai contoh, Anda bisa memulai instalator seperti ini: msiexec /i TortoiseSVN-1.4.0.msi ASPDOTNETHACK=TRUE\n |
| 556 | - | Disable context menu entries | 12950 | Menu konteks Explorer untuk file berversi |
| 557 | - | context menu entries | 12956 | menu konteks |
| 558 | - | disable functions | 12962 | modifikasi |
| 559 | - | Repository Browser | 13113 | Browser Repositori |
| 560 | - | Delete unversioned items | 13163 | Rekursif ke dalam folder tidak berversi |
| 561 | - | The progress dialog which is used for commits, updates and many more commands usually stays open after the command has finished until the user presses the |
13249 | Dialog progres yang digunakan untuk komit, memutahirkan dan banyak perintah lainnya biasanya tetap terbuka sampai perintah selesai dan pengguna menekan tombol |
| 562 | - | To specify a different location of the configuration file, use the parameter . This will override the default path, including any registry setting. | 13255 | Untuk menetapkan lokasi berbeda dari file konfigurasi, gunakan parameter . Ini akan menimpa path standar, termasuk setiap seting registri. |
| 563 | - | To close the progress dialog at the end of a command automatically without using the permanent setting you can pass the parameter. |
13281 | Untuk menutup dialog progres di kahir perintah secara otomatis tanpa menggunakan seting permanen Anda bisa mengoper parameter |
| 564 | - | Shows the about dialog. This is also shown if no command is given. | 13302 | Menampilkan dialog Tentang. Ini juga ditampilkan jika tidak ada perintah yang diberikan. |
| 565 | - | Opens the log dialog. The |
13403 | Membuka dialog log. Path menentukan file atau folder dimana log harus ditampilkan. Tiga opsi tambahan yang bisa di-set: |
| 566 | - | Opens the import dialog. The |
13420 | Membuka dialog impor. Path menetapkan direktori dengan data yang diimpor. |
| 567 | - | Opens the commit dialog. The |
13472 | Membuka dialog komit. Path menetapkan direktori sasaran atau daftar file untuk dikomit. Anda juga bisa menetapkan saklar /logmsg untuk mengoper log pesan yang dibuat ke dialog komit. Atau, jika Anda tidak ingin mengoper log pesan pada baris perintah, gunakan /logmsgfile:path, dimana |
| 568 | - | /noui | 13488 | /noquestion |
| 569 | - | Opens the switch dialog. The |
13515 | Membuka dialog saklar. Path menetapkan direktori target. |
| 570 | - | Exports the working copy in |
13521 | Mengekspor copy pekerjaan dalam |
| 571 | - | Opens the merge dialog. The |
13551 | Membuka dialog log. Path menentukan file atau folder dimana log harus ditampilkan. Tiga opsi tambahan yang bisa di-set: |
| 572 | - | Opens the merge all dialog. The |
13557 | Membuka dialog saklar. Path menetapkan direktori target. |
| 573 | - | Brings up the branch/tag dialog. The |
13563 | Membuka dialog komit. Path menetapkan direktori sasaran atau daftar file untuk dikomit. Anda juga bisa menetapkan saklar /logmsg untuk mengoper log pesan yang dibuat ke dialog komit. Atau, jika Anda tidak ingin mengoper log pesan pada baris perintah, gunakan /logmsgfile:path, dimana |
| 574 | - | /line:xxx | 13596 | /rev:xxx |
| 575 | - | Starts the external diff program specified in the TortoiseSVN settings. The |
13602 | Memulai program eksternal diff yang ditetapkan dalam seting TortoiseSVN. |
| 576 | - | Starts the conflict editor specified in the TortoiseSVN settings with the correct files for the conflicted file in |
13616 | Memulai editor konflik dalam seting TortoiseSVN dengan file yang benar untuk file yang konflik dalam |
| 577 | - | /remote | 13632 | hilangkan |
| 578 | - | Check repository | 13638 | Repositori |
| 579 | - | Opens the check-for-modifications dialog. The |
13644 | Membuka dialog checkout. |
| 580 | - | Starts the repository browser dialog, pointing to the URL of the working copy given in |
13661 | Memulai dialog browser repositori, merujuk ke URL dari copy pekerjaan yang diberikan dalam |
| 581 | - | Adds all targets in |
13672 | Menambah semua target dalam |
| 582 | - | Locks a file or all files in a directory given in |
13719 | Mengunci sebuah file atau semua file dalam sebuah direktori. Dialog 'kunci' ditampilkan agar pengguna bisa memasukan komentar untuk penguncian. |
| 583 | - | Unlocks a file or all files in a directory given in |
13724 | Buka kunci sebuah file atau semua file dalam suatu direktori.. |
| 584 | - | Rebuilds the windows icon cache. Only use this in case the windows icons are corrupted. A side effect of this (which can't be avoided) is that the icons on the desktop get rearranged. To suppress the message box, pass |
13730 | Membangun ulang ikon cache jendela. Gunakan ini bila ikon jendela rusak. Efek samping dari ini (yang tidak dapat dihindari) adalah bahwa ikon-ikon pada desktop diatur ulang. |
| 585 | - | URL handler | 13770 | URL berubah |
| 586 | - | The following commands are allowed with |
13796 | TortoiseSVN mempunyai beberapa properti khusus, dan ini dimulai dengan |
| 587 | - | If you think you have found a bug in TortoiseSVN, we may ask you to try to reproduce it using the CLI, so that we can distinguish TortoiseSVN issues from Subversion issues. This reference tells you which command to try. | 13897 | Jika Anda berpikir telah menemukan bug dalam TortoiseSVN, kami mungkin meminta Anda untuk mencoba membuat ulang menggunakan CLI, agar kami bisa membedakan isu TSVN dari isu Subversion. Referensi ini memberitahu Anda perintah mana yang dicoba. |
| 588 | - | In the descriptions which follow, the URL for a repository location is shown simply as |
13908 | Dalam penjelasan berikut, URL untuk lokasi repositori ditampilkan cukup sebagai |
| 589 | - | If you use Diff from the main context menu, you are diffing a modified file against its BASE revision. The output from the CLI command above also does this and produces output in unified-diff format. However, this is not what TortoiseSVN is using. TortoiseSVN uses TortoiseMerge (or a diff program of your choosing) to display differences visually between full-text files, so there is no direct CLI equivalent. | 14075 | Jika Anda menggunakan Diff dari menu konteks utama, Anda melakukan diff file yang diubah terhadap revisi BASE-nya. Output dari perintah CLI di atas juga melakukan ini dan menghasilkan output dalam format unified-diff. Akan tetapi, ini bukan apa yang digunakan TortoiseSVN. TortoiseSVN menggunakan TortoiseMerge (atau program diff pilihan Anda) untuk menampilkan perbedaan secara visual antara file teks lengkap, agar tidak ada persamaan CLI langsung. |
| 590 | - | The |
14344 | |
| 591 | - | \n svnadmin create --fs-type fsfs PATH\n |
14410 | \n svnadmin create --fs-type fsfs PATH\n or\n svnadmin create --fs-type bdb PATH\n |
| 592 | - | If you use TortoiseBlame to view the blame info, the file log is also required to show log messages in a tooltip. If you view blame as a text file, this information is not required. | 14449 | Jika Anda menggunakan TortoiseBlame untuk melihat info blame, log file juga diperlukan untuk menampilkan pesan log dalam tooltip. Jika Anda melihat blame sebagai file teks, informasi ini tidak diperlukan. |
| 593 | - | Because the |
14474 | Karena properti svn:ignore sering bernilai multi-baris, ia ditampikan disini sebagai sedang diubah via file teks daripada secara langsung pada baris perintah. |
| 594 | - | TortoiseSVN creates a patch file in unified diff format by comparing the working copy with its BASE version. | 14490 | TortoiseSVN membuat patchfile dalam format unified diff dengan membandingkan copy pekerjaan dengan revisi BASE-nya. |
| 595 | - | This appendix contains a more detailed discussion of the implementation of some of TortoiseSVN's features. | 14505 | Apendiks ini berisi solusi terhadap masalah/pertanyaan yang mungkin Anda punyai saat menggunakan TortoiseSVN. |
| 596 | - | 14531 | ||
| 597 | - | In fact, you may find that not all of these icons are used on your system. This is because the number of overlays allowed by Windows is limited to 15. Windows uses 4 of those, and the remaining 11 can be used by other applications. If there are not enough overlay slots available, TortoiseSVN tries to be a Good Citizen (TM)and limits its use of overlays to give other apps a chance. |
14569 | Kenyataannya, Anda mungkin menemukan bahwa tidak semua ikon ini digunakan pada sistem Anda. Ini dikarenakan jumlah lapisan yang dibolehkan oleh Windows dibatasi hanya 15. Windows menggunakan 4 dari itu, dan sisanya 11 bisa digunakan oleh aplikasi lain. Jika Anda juga menggunakan TortoiseCVS, maka slot lapisan ikon tidak cukup tersedia, maka TortoiseSVN mencoba menjadi Warga Yang Baik (TM)dan membatasi penggunaan lapisan untuk memberikan kesempatan bagi aplikasi lain. |
| 598 | - | 14575 | ||
| 599 | - | 14581 | ||
| 600 | - | 14587 | ||
| 601 | - | 14593 | ||
| 602 | - | 14599 | ||
| 603 | - | SSH Configuration Variants | 14803 | Konfigurasi |
| 604 | - | A term frequently used in revision control systems to describe what happens when development forks at a particular point and follows 2 separate paths. You can create a branch off the main development line so as to develop a new feature without rendering the main line unstable. Or you can branch a stable release to which you make only bug fixes, while new developments take place on the unstable trunk. In Subversion a branch is implemented as a cheap copy. |
14884 | Batasan yang sering digunakan dalam sistem kontrol revisi untuk menjelaskan apa yang terjadi ketika garpu pengembangan pada titik tertentu dan mengikuti 2 path terpisah. Anda bisas membuat cabang diluar baris pengembangan utama untuk mengembangkan fitur baru tanpa menyerempet barus utama yang tidak stabil. Atau Anda bisa mencabangkan rilis stabil ke mana Anda hanya membuat pembetulan bug, sementara pengembangan baru menempati batang tidak stabil. Dalam Subversion cabang diimplementasikan sebagai copy murah. |
| 605 | - | To quote from the Subversion book: Recursively clean up the working copy, removing locks and resuming unfinished operations. If you ever get aNote that in this context |
14895 | Mengutip dari buku Subversion: Secara rekursif membersihkan copy pekerjaan, menghapus kuncian dan melanjutkan operasi yang belum selesai. Jika Anda pernah mendapatkan kesalahanCatatan bahwa konteks kuncimerujuk ke penguncian sistem file lokal, bukan penguncian repositori. |
| 606 | - | When you delete a versioned item (and commit the change) the item no longer exists in the repository after the committed revision. But of course it still exists in earlier repository revisions, so you can still access it. If necessary, you can copy a deleted item and resurrectit complete with history. |
14926 | Ketika Anda menghapus item berversi (dan komit perubahan) item tidak lagi ada dalam repositori setelah revisi yang dikomit. Tapi tentunya masih ada dalam revisi repositori sebelumnya, dan Anda masih bisa mengaksesnya. Jika perlu, Anda bisa mengcopy item yang dihapus dan menghidupkannyasepenuhnya dengan histori. |
| 607 | - | A proprietary Subversion filesystem backend for repositories. Can be used on network shares. Default for 1.2 and newer repositories. | 14947 | FS Filesystem. Hak milik Subversion filesystem backend untuk repositori. Bisa digunakan pada jaringan berbagi. Standar untuk 1.2 dan repositori lebih baru. |
| 608 | - | When you take out a lock on a versioned item, you mark it in the repository as non-committable, except from the working copy where the lock was taken out. | 14973 | Ketika Anda membawa kuncian pada item berversi, Anda menandainya dalam repositori sebagai tidak bisa dikomit, kecuali dari copy pekerjaan dimana kuncian tersebut dibawa. |
Total:608
This test check if all escaped chars are known and its using match with English. Even you get red here it may be legal for your language.
This test is in developing now. Ignored are: \r \n (wee new line style test) and \".
| Index | Line | English | Line | Native |
| 1 | Developer B moves <filename>Foo.c</filename> to <filename>Bix.c</filename> | 3147 | Buat folder lain <filename>MyNewRepository</filename> di dalam <filename>D:\\SVN\\</filename>. |
Total:1
PASS
Next few sections informs about duplicate accelerators in translation. There is no reason to be stressed about this, but some translators like to know it. In a fact even English translation contains duplicate.
RC checking is currently off for this language. If you like enable it for your translation drop me an email.
