Примери коришћења Your working copy на Енглеском и њихови преводи на Српски
{-}
-
Colloquial
-
Ecclesiastic
-
Computer
-
Latin
-
Cyrillic
Patch files are applied to your working copy.
Update Your Working Copy With Changes From Others Update.
It will not show changes newer than your working copy.
In particular, your working copy contains a subdirectory named.
This is based on information obtained when you update your working copy.
Normally you update your working copy using TortoiseSVN→ Update.
Select a directory in windows explorer where you want to place your working copy.
To add files from outside your working copy you can use the drag-and-drop handler.
This is a fast andeasy way to remove all generated files in your working copy.
Sending the changes you made to your working copy is known as committing the changes.
If your working copy is up to date and there are no conflicts, you are ready to commit your changes.
Right click on the folder(s)you would like to add to your working copy, then use Context menu→ Update.
C will appear in your working copy, and your change will still be present in button.c.
Patch files are simply Unified-Diff files showing the differences between your working copy and the base revision.
In order to apply a patch file to your working copy, you need to have at least read access to the repository.
If the external item is renamed at some point in the future then Subversion will not be able to update this item in your working copy.
Find the sub-folder you would like to add to your working copy, then use Context Menu→ Update item to revision….
Suppose your working copy is at revision 100, but you want it to reflect the state which it had in revision 50- then simply update to revision 50.
This opens a new dialog where you can check all items you want in your working copy and uncheck all the items you don't want.
Select the file(s) in your working copy for which you want to acquire a lock, then select the command TortoiseSVN→ Get Lock….
If a Subversion command cannot complete successfully,perhaps due to server problems, your working copy can be left in an inconsistent state.
Put another way,you need to relocate when your working copy is referring to the same location in the same repository, but the repository itself has moved.
Chapter 6, The SubWCRev Program is a separate program included with TortoiseSVN which can extract the information from your working copy and write it into a file.
If you want to see what changes you have made in your working copy, just use the explorer context menu and select TortoiseSVN→ Diff.
In your working copy, you can change files' contents, create, delete, rename and copy files and directories, and then commit the complete set of changes as a unit.
The standard Update command has no options andjust updates your working copy to the HEAD revision of the repository, which is the most common use case.
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.
The remote developer's patch has now been applied to your working copy, so you need to commit to allow everyone else to access the changes from the repository.
You can check out an external at its HEAD revision,so when the external item changes in the repository, your working copy will receive those changes on update.
If you want to export your working copy tree structure but containing only the files which are locally modified, refer to SVN Export changed items here above.